This recipe demonstrates a basic cloud networking setup for HPC on AWS. Several other recipes can consume the VPC and subnets configured by this recipe.
It is most useful when your HPC cluster meets these criteria:
- You only launch instances in one Availability Zone (this is fairly standard)
- You don't need that many instances - the default configuration provided by this template creates subnets with 250 available IP addresses.
This template creates one public and one private subnet in the same Availability Zone.
- Create Public and Private subnets. The only required parameter is Availabilty Zone if you want to create a new VPC.
If you don't wish to use the quick-create links, you can also download the assets/public-private.yaml file and uploading it to the AWS CloudFormation console.
Once your networking stack has been created, you may wish to activate termination protection for it since you may come to depend on the network assets it creates.
The template exports several variables, namedspaced by stack name. This lets you import them into other stacks.
- VPC - the pre-existing or provisioned VPC
- DefaultPublicSubnet - the public subnet in the VPC
- DefaultPrivateSubnet - the private subnet in the VPC
- InternetGatewayId - the pre-existing or provisioned internet gateway for the VPC
- VPC and Subnets - No Charge
- Internet Gateway - No charge, but you pay a small amount for traffic passing out of the VPC.
- NAT Gateway - There is a region-specific hourly cost for the NAT gatway, plus a charge for data sent through the gateway.
See AWS VPC pricing for details.
When you are done using this networking configuration, you can delete it by navigating to the AWS CloudFormation console and deleting the relevant stack. If you have enabled termination protection, you will need to disable it first.