...
Abiquo configures VPC networking Scenario 2 as described in the AWS documentation. See https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html.
Abiquo creates VPCs with NAT support.
...
When creating a NAT gateway, Abiquo will reuse floating IPs that are not assigned to a VDC.
...
Abiquo creates a route table that is equivalent to the AWS route table with the values of the Abiquo private network.
...
Abiquo creates VPCs with a public subnet.
...
Abiquo creates a VPC in AWS with one Availability zone only. When you create this in AWS using the wizard, it creates three routing tables, but Abiquo creates two and marks the private routing table as Main.
Abiquo creates a public subnet where the name is the AWS Subnet ID, in the format subnet-xxxx, which is the provider ID for the public subnet. The NAT gateway that AWS creates in a VPC uses a private IP in the public subnet.
The primary private IP of the NAT gateway is automatically assigned by AWS. In Abiquo we always set the first IP as the gateway, because according to the documentation, it is reserved for the VPC router. See https://docs.aws.amazon.com/vpc/latest/userguide/subnet-sizing.html
In Abiquo the public IP of the NAT gateway enables access to the internet from the private subnet, but it does not allow incoming connections.
To connect from outside the VPC, you will need at least one VM with an IP address in the public subnet, and one public IP. To allow connections to your VM via the public IP, AWS automatically creates a DNAT rule using the internet gateway.
When you create a VPC in Abiquo, it does not onboard the IPs of the private subnets. You need to synchronize each network to onboard its IPs.
...
Technical notes about AWS networks
When creating a NAT gateway, Abiquo will reuse floating IPs that are not assigned to a VDC.
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 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.
Abiquo creates VPCs with a private subnet.
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 Elastic IPs via 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. To deploy to different Availability zones, create a private networks (VPC subnet) for each zone.
The private subnets in the same availability zone as a public subnet will have internet access through the public subnet.
...
Abiquo creates a VPC with a minimum network size of /16 and a subnet of size /24
...
, or with the sizes defined by the user
...
The default CIDR for the VPC and the subnet is 192.168.0.0, which is the default private network in Abiquo.
You can set a custom private network in Abiquo and this network will be used to create the VPC and subnet in Abiquo.
You can create multiple address spaces (called Abiquo address ranges) and Abiquo private networks in different availability zones in the same VPC.
AWS reserves
...
Abiquo supports the AWS gateway address as the first address in a network.AWS reserves the first four IP addresses and the last IP address of a VPC private connect network.
For a network that is defined to start with address 0:
The, the first available IP address will be address 4
Theand the gateway address is address 1.
Abiquo supports multiple IP addresses per VM in the AWS integration.
You can synchronize existing VMs and create new IP addresses through Abiquo, including multiple Elastic IPs.
The maximum number of IP addresses is determined by the AWS hardware profile (instance type). See https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI
Abiquo adds IPs in the same subnet to the same elastic network interface.
For information about Elastic Network Interfaces, see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html
...