...
- By default, VMs in private networks will have internet access through the public subnet. So a VM can connect to the internet to download its configuration, for example, using Chef, without an Elastic IP.
- Users can create public subnets and Abiquo will assign them to route tables with a route to the internet gateway.
- When Abiquo creates new public subnets, it will not create any new NAT gateways.
- If users delete the original public subnet, this will also delete the original NAT gateway. But Abiquo will replace all the routes in the main route table that route traffic to the deleted NAT gateway with a new rule to route traffic to the internet gateway.
You can acquire public IPs for your virtual datacenter and in AWS these will be Elastic IPs with public network addresses.
Abiquo users must attach Elastic IPs to VMs with a connection to the a public subnet.
Note that AWS may charge for Elastic IPs when they are NOT in use, i.e. when they are not assigned to a VM or when the VM is not deployed in AWS.
Elastic IPs are defined in Abiquo as "floating IPs". Abiquo manages them like public IPs but they do not belong to any Abiquo network.
...
- The private subnet is a private connect network.
- The private subnet has an Internet gateway and access to the VPC from outside the cloud is through NAT or Elastic IPs via the a public subnet.
- Within your virtual datacenter, you can create more Abiquo private networks (subnets in your VPC), so you can deploy to different Availability Zones.
- The private subnets in the same availability zone as the a public subnet will have internet access through the public subnet.
...