Readonly
inboundReadonly
nameThe name of the Network ACL.
CAUTION: Changing this property value causes the network ACL to be recreated. Please be aware that any downstream dependencies may cause this property update to fail. Please also note that your network traffic may be temporarily impacted while the ACL is updated.
Readonly
outboundReadonly
subnetA list of subnets to associate with the Network ACL
This is the logical name
property of the subnet as defined in network-config.yaml.
Readonly
tags(OPTIONAL) A list of tags to attach to the Network ACL
Generated using TypeDoc
NetworkConfig / VpcConfig | VpcTemplatesConfig / NetworkAclConfig
Network access control list (ACL) configuration. Use this configuration to define custom network ACLs for your VPC. A network ACL allows or denies specific inbound or outbound traffic at the subnet level. Network ACLs are stateless, which means that responses to allowed inbound traffic are subject to the rules for outbound traffic (and vice versa).
The following example shows an inbound and outbound rule that would allow inbound SSH traffic from the CIDR range 10.0.0.0/16.
Example