DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.

DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Only ACL allow rules are supported as part of Network ACLs. Default is to block all incoming and all outgoing traffic between tiers and between tiers and various gateways (including Public). ACL deny rules will be supported. New fields "number" and "action"will be added to rules to resolve conflicting rules. After rule creation, its number can be modified. NetworkACLs will be evaluated in the order of its number . starting from lowest. Action of the matching rule is applied.
NetworkACLContainer will be introduced to manage NetworkACLs.
NetworkACLContainer is a set of NetworkACLs that can be assigned to any vpc tier. Instead of adding NetworkACLs directly to the tier, NetworkACLs will be added to the NetworkACLContainer. NetworkACLContainer can be assigned to multiple vpc tiers. Each tier can be associated with only one NetworkACLContainer.
...
NetworkACLs can be added or removed from the container using APIs addACLtoContaineraddNetworkACLtoContainer, removeNetworkACLfromContainer
...
createNetworkAcl:
...
replaceNetworkACL:
createNetworkAclContainer
Parameters:
Response:
...
Response
Response:
New columns in firewall_rules table:
...