Create virtual datacenters in AWS without NAT

1 Create an AWS VDC without NAT
2 Create a public subnet
3 Create a NAT gateway in AWS
4 Virtual datacenter with a NAT gateway
5 Change to AWS resource names

Create an AWS VDC without NAT

From Abiquo 6.1.2, as in private cloud, the user can now select if they want to create networks when they create a virtual datacenter in AWS.

If the user chooses not to create networks when they create the VDC, Abiquo will not create the public subnet, internet gateway, or the NAT gateway with an elastic IP.

An AWS VDC with no networks and no public IP for NAT

When the user selects the None option, then they must still enter the address range for the VPC network.

Create a virtual datacenter with no network in AWS

If you do not create the networks when you create the VDC:

To connect to a VM, create a public subnet with an IP address before you add a public IP
To add NAT for outward internet connectivity for your VDC, create a NAT gateway directly in AWS.

The following sections describe how to do do these steps.

Create a public subnet

To connect to a VM in an AWS VDC with the None option for networks, create a public subnet.

In your virtual datacenter, go to Network → Private
Click + add and complete the dialog, selecting the Internet gateway checkbox.

You can now add an IP from the public subnet and a public IP to your VM as usual.
For more details, see How to deploy a VM in AWS using Abiquo.

When you create a public subnet, if there is no internet gateway, the platform creates a new one and associates it with a new route table. If an internet gateway exists but it is not associated with a route table with a destination of 0.0.0.0/0, then the platform creates a new route table.

Create a NAT gateway in AWS

To allow an outbound internet connection for private subnets, the user will need to create a public subnet, and a private network in the VDC, then manually create the NAT gateway in the AWS console (see AWS documentation at Create a NAT gateway), and edit the main route table to add a new route with target = igw and destination 0.0.0.0/0.

Virtual datacenter with a NAT gateway

The following screenshots show resources in the default configuration with a public subnet and a NAT gateway.

Change to AWS resource names

From Abiquo 6.1.2, the platform will name all resources that it creates for the VPC with the VDC name as a prefix. This includes subnets (except default_private_network), route table, internet gateway, NAT gateway, and the elastic IP used for the NAT gateway.