There are two important concepts to understand when using AWS CloudFormation: templates and stacks. A template is used to describe your AWS resources and their properties. When you create a stack, AWS CloudFormation provisions the resources that are described in the template.

To learn more, view the AWS documentation on stacks and templates.

Rackspace CloudFormation Template: BaseNetwork

In our Aviator service level we assist customers with creating custom CloudFormation templates to describe their environments. For customers at both the Navigator and Aviator service levels we make a standardized CloudFormation Template, BaseNetwork, available to create the initial network and all of its necessary components. The rest of this section will describe the elements that are part of the BaseNetwork CloudFormation Template, and their associated components. You can download the BaseNetwork template here.


  • VPCCIDR - CIDR for the VPC

  • SubnetPublicAZ1 - CIDR for Public subnet

  • SubnetPublicAZ2 - CIDR for Public subnet

  • SubnetPrivateAZ1 - CIDR for Private subnet

  • SubnetPrivateAZ2 - CIDR for Private subnet

  • InstanceTenancy - Single or Multi-Tenant Hypervisor

  • Environment - Dev, Test, Prod etc.


  • The CloudFormation template has two major options:

    • 2 Availability Zones with 4 Subnets

    • 3 Availability Zones with 6 Subnets


  • High Availability NAT gateways get created in the public subnets (1 per AZ)

    • NatAZ1

    • NatAZ2

    • NatAZ3 (if necessary)


  • Service Provider - “Rackspace”

  • Environment - from Parameter Environment

  • Name - Resource name (e.g. IGWBase, SubnetPublicAZ2)


  • outputVPCID

  • outputSubnetPublicAZ1

  • outputSubnetPublicAZ2

  • outputSubnetPublicAZ3 (if necessary)

  • outputSubnetPrivateAZ1

  • outputSubnetPrivateAZ2

  • outputSubnetPrivateAZ3 (if necessary)