Page History

...

• add ruleAction/ruleNumber to createNetworkACL api
• implement replaceNetworkACL API
• For existing customers, for all network ACL db entries, add "ruleAction = allow" and "ruleNumber". Rule number should be calculated based on rule DB id.
• introduce networkACLList concept - list of network ACL rules that can be associated with a particular network. CreateNetworkACL will continue having networkId parameter (We'll just make it optional to provide backwards compatibility). Plug new parameterwill be added - networkACLListId (also optional).If no networkACLListId is specified, the networkACL will be added to the default container (list) of the network.
•  New api replaceNetworkACLList will be used to change network->ACL association

5. Ability to extend VPC network ip ranges

As in CS isolated networks we have no support for extending ip ranges, we can't do it in the VPC networks as Amazon does. So no analogs for following EC2 VPC commands:

• AssignPrivateIpAddress
• UnassignPrivateIpAddress

6. Ability to add/remove existing networks to VPC

In order to be used in VPC, network has to be created fresh in the VPC. We can't attach/detach existing networks to/from VPC the way amazon lets you:

http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-AttachNetworkInterface.html

http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DetachNetworkInterface.html