README.md

April 29, 2026 · View on GitHub

This component is responsible for provisioning a VPC and corresponding Subnets with advanced configuration capabilities.

Key Features:

Independent control over public and private subnet counts per Availability Zone
Flexible NAT Gateway placement (index-based or name-based)
Named subnets with different naming schemes for public vs private
Cost optimization through strategic NAT Gateway placement
VPC Flow Logs support for auditing and compliance
VPC Endpoints for AWS services (S3, DynamoDB, and interface endpoints)
AWS Shield Advanced protection for NAT Gateway EIPs (optional)

What's New in v3.1.0:

Uses terraform-aws-dynamic-subnets v3.1.0 with enhanced subnet configuration
Separate public/private subnet counts and names per AZ
Precise NAT Gateway placement control for cost optimization
NAT Gateway IDs and private IPs exposed in subnet stats outputs
Requires AWS Provider v5.0+

Tip

👽 Use Atmos with Terraform

Cloud Posse uses atmos to easily orchestrate multiple environments using Terraform.
Works with Github Actions, Atlantis, or Spacelift.

Watch demo of using Atmos with Terraform

Example of running atmos to manage infrastructure from our Quick Start tutorial.

Basic Configuration

Here's a basic example using legacy configuration (fully backward compatible):

# catalog/vpc/defaults
components:
  terraform:
    vpc/defaults:
      metadata:
        type: abstract
        component: vpc
      settings:
        spacelift:
          workspace_enabled: true
      vars:
        enabled: true
        name: vpc
        availability_zones:
          - "a"
          - "b"
          - "c"
        nat_gateway_enabled: true
        nat_instance_enabled: false
        max_subnet_count: 3
        vpc_flow_logs_enabled: true
        vpc_flow_logs_bucket_environment_name: <environment>
        vpc_flow_logs_bucket_stage_name: audit
        vpc_flow_logs_traffic_type: "ALL"
        subnet_type_tag_key: "example.net/subnet/type"
        # Legacy subnet configuration (still supported)
        subnets_per_az_count: 1
        subnets_per_az_names: ["common"]

# stacks/ue2-dev.yaml
import:
  - catalog/vpc

components:
  terraform:
    vpc:
      metadata:
        component: vpc
        inherits:
          - vpc/defaults
      vars:
        ipv4_primary_cidr_block: "10.111.0.0/18"

Cost-Optimized NAT Configuration

Reduce NAT Gateway costs by placing NAT Gateways in only one public subnet per AZ:

components:
  terraform:
    vpc:
      vars:
        # Create 2 public subnets per AZ
        public_subnets_per_az_count: 2
        public_subnets_per_az_names: ["loadbalancer", "web"]

        # Create 3 private subnets per AZ
        private_subnets_per_az_count: 3
        private_subnets_per_az_names: ["app", "database", "cache"]

        # Place NAT Gateway ONLY in the first public subnet (index 0)
        # This saves ~67% on NAT Gateway costs compared to NAT in all public subnets
        nat_gateway_public_subnet_indices: [0]

Cost Savings Example (3 AZs, us-east-1):

Without optimization: 6 NAT Gateways (2 per AZ) = ~$270/month
With optimization: 3 NAT Gateways (1 per AZ) = ~$135/month
Monthly Savings: ~~$135 (~~$1,620/year)

Important: You can use EITHER nat_gateway_public_subnet_indices OR nat_gateway_public_subnet_names, but not both. The plan will fail if both are specified.

Named NAT Gateway Placement

Place NAT Gateways by subnet name instead of index:

components:
  terraform:
    vpc:
      vars:
        # Must specify both count and names when using named subnets
        public_subnets_per_az_count: 2
        public_subnets_per_az_names: ["loadbalancer", "web"]
        private_subnets_per_az_count: 2
        private_subnets_per_az_names: ["app", "database"]

        # Place NAT Gateway only in "loadbalancer" subnet
        nat_gateway_public_subnet_names: ["loadbalancer"]

Important: When using public_subnets_per_az_names or private_subnets_per_az_names, you must also specify the corresponding count variables (public_subnets_per_az_count / private_subnets_per_az_count).

High-Availability NAT Configuration

For production environments requiring redundancy:

components:
  terraform:
    vpc:
      vars:
        public_subnets_per_az_count: 2
        nat_gateway_public_subnet_indices: [0, 1]  # NAT in both public subnets per AZ

Separate Public/Private Subnet Architecture

Different subnet counts and names for public vs private:

components:
  terraform:
    vpc:
      vars:
        # 2 public subnets per AZ for load balancers and public services
        public_subnets_per_az_count: 2
        public_subnets_per_az_names: ["alb", "nat"]

        # 4 private subnets per AZ for different application tiers
        private_subnets_per_az_count: 4
        private_subnets_per_az_names: ["web", "app", "data", "cache"]

        # NAT Gateway in "nat" subnet
        nat_gateway_public_subnet_names: ["nat"]

VPC Endpoints Configuration

Add VPC Endpoints for AWS services to reduce data transfer costs and improve security:

components:
  terraform:
    vpc:
      vars:
        # Gateway endpoints (no hourly charges)
        gateway_vpc_endpoints:
          - "s3"
          - "dynamodb"

        # Interface endpoints (hourly charges apply)
        interface_vpc_endpoints:
          - "ec2"
          - "ecr.api"
          - "ecr.dkr"
          - "logs"
          - "secretsmanager"

Complete Production Example

components:
  terraform:
    vpc:
      vars:
        enabled: true
        name: vpc
        ipv4_primary_cidr_block: "10.0.0.0/16"

        availability_zones:
          - "a"
          - "b"
          - "c"

        # Public subnets for ALB and NAT
        public_subnets_per_az_count: 2
        public_subnets_per_az_names: ["loadbalancer", "nat"]

        # Private subnets for different tiers
        private_subnets_per_az_count: 3
        private_subnets_per_az_names: ["app", "database", "cache"]

        # Cost-optimized NAT placement
        nat_gateway_enabled: true
        nat_gateway_public_subnet_names: ["nat"]

        # VPC Flow Logs
        vpc_flow_logs_enabled: true
        vpc_flow_logs_bucket_environment_name: mgmt
        vpc_flow_logs_bucket_stage_name: audit
        vpc_flow_logs_traffic_type: "ALL"

        # VPC Endpoints
        gateway_vpc_endpoints:
          - "s3"
          - "dynamodb"
        interface_vpc_endpoints:
          - "ecr.api"
          - "ecr.dkr"
          - "logs"

        subnet_type_tag_key: "example.net/subnet/type"

Important

In Cloud Posse's examples, we avoid pinning modules to specific versions to prevent discrepancies between the documentation and the latest released versions. However, for your own projects, we strongly advise pinning each module to the exact version you're using. This practice ensures the stability of your infrastructure. Additionally, we recommend implementing a systematic approach for updating versions to avoid unexpected changes.

Requirements

Name	Version
terraform	>= 1.0.0
aws	>= 5.0.0
null	>= 3.0

Providers

Name	Version
aws	>= 5.0.0
null	>= 3.0

Modules

Name	Source	Version
endpoint_security_groups	cloudposse/security-group/aws	2.2.0
iam_roles	../account-map/modules/iam-roles	n/a
subnets	cloudposse/dynamic-subnets/aws	3.1.1
this	cloudposse/label/null	0.25.0
utils	cloudposse/utils/aws	1.4.0
vpc	cloudposse/vpc/aws	3.0.0
vpc_endpoints	cloudposse/vpc/aws//modules/vpc-endpoints	3.0.0
vpc_flow_logs_bucket	cloudposse/stack-config/yaml//modules/remote-state	2.0.0

Resources

Name	Type
aws_flow_log.default	resource
aws_shield_protection.nat_eip_shield_protection	resource
null_resource.nat_placement_validation	resource
aws_caller_identity.current	data source
aws_eip.eip	data source

Inputs

Name	Description	Type	Default	Required
additional_tag_map	Additional key-value pairs to add to each map in `tags_as_list_of_maps`. Not added to `tags` or `id`. This is for some rare cases where resources want additional configuration of tags and therefore take a list of maps with tag key, value, and additional configuration.	`map(string)`	`{}`	no
assign_generated_ipv6_cidr_block	When `true`, assign AWS generated IPv6 CIDR block to the VPC. Conflicts with `ipv6_ipam_pool_id`.	`bool`	`false`	no
attributes	ID element. Additional attributes (e.g. `workers` or `cluster`) to add to `id`, in the order they appear in the list. New attributes are appended to the end of the list. The elements of the list are joined by the `delimiter` and treated as a single ID element.	`list(string)`	`[]`	no
availability_zone_ids	List of Availability Zones IDs where subnets will be created. Overrides `availability_zones`. Can be the full name, e.g. `use1-az1`, or just the part after the AZ ID region code, e.g. `-az1`, to allow reusable values across regions. Consider contention for resources and spot pricing in each AZ when selecting. Useful in some regions when using only some AZs and you want to use the same ones across multiple accounts.	`list(string)`	`[]`	no
availability_zones	List of Availability Zones (AZs) where subnets will be created. Ignored when `availability_zone_ids` is set. Can be the full name, e.g. `us-east-1a`, or just the part after the region, e.g. `a` to allow reusable values across regions. The order of zones in the list must be stable or else Terraform will continually make changes. If no AZs are specified, then `max_subnet_count` AZs will be selected in alphabetical order. If `max_subnet_count > 0` and `length(var.availability_zones) > max_subnet_count`, the list will be truncated. We recommend setting `availability_zones` and `max_subnet_count` explicitly as constant (not computed) values for predictability, consistency, and stability.	`list(string)`	`[]`	no
context	Single object for setting entire context at once. See description of individual variables for details. Leave string and numeric variables as `null` to use default value. Individual variable settings (non-null) override settings in context object, except for attributes, tags, and additional_tag_map, which are merged.	`any`	{ "additional_tag_map": {}, "attributes": [], "delimiter": null, "descriptor_formats": {}, "enabled": true, "environment": null, "id_length_limit": null, "label_key_case": null, "label_order": [], "label_value_case": null, "labels_as_tags": [ "unset" ], "name": null, "namespace": null, "regex_replace_chars": null, "stage": null, "tags": {}, "tenant": null }	no
delimiter	Delimiter to be used between ID elements. Defaults to `-` (hyphen). Set to `""` to use no delimiter at all.	`string`	`null`	no
descriptor_formats	Describe additional descriptors to be output in the `descriptors` output map. Map of maps. Keys are names of descriptors. Values are maps of the form `{<br/> format = string<br/> labels = list(string)<br/>}` (Type is `any` so the map values can later be enhanced to provide additional options.) `format` is a Terraform format string to be passed to the `format()` function. `labels` is a list of labels, in order, to pass to `format()` function. Label values will be normalized before being passed to `format()` so they will be identical to how they appear in `id`. Default is `{}` (`descriptors` output will be empty).	`any`	`{}`	no
enabled	Set to false to prevent the module from creating any resources	`bool`	`null`	no
environment	ID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'	`string`	`null`	no
gateway_vpc_endpoints	A list of Gateway VPC Endpoints to provision into the VPC. Only valid values are "dynamodb" and "s3".	`set(string)`	`[]`	no
id_length_limit	Limit `id` to this many characters (minimum 6). Set to `0` for unlimited length. Set to `null` for keep the existing setting, which defaults to `0`. Does not affect `id_full`.	`number`	`null`	no
interface_vpc_endpoints	A list of Interface VPC Endpoints to provision into the VPC.	`set(string)`	`[]`	no
ipv4_additional_cidr_block_associations	IPv4 CIDR blocks to assign to the VPC. `ipv4_cidr_block` can be set explicitly, or set to `null` with the CIDR block derived from `ipv4_ipam_pool_id` using `ipv4_netmask_length`. Map keys must be known at `plan` time, and are only used to track changes.	map(object({ ipv4_cidr_block = string ipv4_ipam_pool_id = string ipv4_netmask_length = number }))	`{}`	no
ipv4_cidr_block_association_timeouts	Timeouts (in `go` duration format) for creating and destroying IPv4 CIDR block associations	object({ create = string delete = string })	`null`	no
ipv4_cidrs	Lists of CIDRs to assign to subnets. Order of CIDRs in the lists must not change over time. Lists may contain more CIDRs than needed.	list(object({ private = list(string) public = list(string) }))	`[]`	no
ipv4_primary_cidr_block	The primary IPv4 CIDR block for the VPC. Either `ipv4_primary_cidr_block` or `ipv4_primary_cidr_block_association` must be set, but not both.	`string`	`null`	no
ipv4_primary_cidr_block_association	Configuration of the VPC's primary IPv4 CIDR block via IPAM. Conflicts with `ipv4_primary_cidr_block`. One of `ipv4_primary_cidr_block` or `ipv4_primary_cidr_block_association` must be set. Additional CIDR blocks can be set via `ipv4_additional_cidr_block_associations`.	object({ ipv4_ipam_pool_id = string ipv4_netmask_length = number })	`null`	no
label_key_case	Controls the letter case of the `tags` keys (label names) for tags generated by this module. Does not affect keys of tags passed in via the `tags` input. Possible values: `lower`, `title`, `upper`. Default value: `title`.	`string`	`null`	no
label_order	The order in which the labels (ID elements) appear in the `id`. Defaults to ["namespace", "environment", "stage", "name", "attributes"]. You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.	`list(string)`	`null`	no
label_value_case	Controls the letter case of ID elements (labels) as included in `id`, set as tag values, and output by this module individually. Does not affect values of tags passed in via the `tags` input. Possible values: `lower`, `title`, `upper` and `none` (no transformation). Set this to `title` and set `delimiter` to `""` to yield Pascal Case IDs. Default value: `lower`.	`string`	`null`	no
labels_as_tags	Set of labels (ID elements) to include as tags in the `tags` output. Default is to include all labels. Tags with empty values will not be included in the `tags` output. Set to `[]` to suppress all generated tags. Notes: The value of the `name` tag, if included, will be the `id`, not the `name`. Unlike other `null-label` inputs, the initial setting of `labels_as_tags` cannot be changed in later chained modules. Attempts to change it will be silently ignored.	`set(string)`	[ "default" ]	no
map_public_ip_on_launch	Instances launched into a public subnet should be assigned a public IP address	`bool`	`true`	no
max_nats	Upper limit on number of NAT Gateways/Instances to create. Set to 1 or 2 for cost savings at the expense of availability. Default creates a NAT Gateway in each public subnet.	`number`	`null`	no
max_subnet_count	Sets the maximum amount of subnets to deploy. 0 will deploy a subnet for every provided availability zone (in `region_availability_zones` variable) within the region	`number`	`0`	no
name	ID element. Usually the component or solution name, e.g. 'app' or 'jenkins'. This is the only ID element not also included as a `tag`. The "name" tag is set to the full `id` string. There is no tag with the value of the `name` input.	`string`	`null`	no
namespace	ID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally unique	`string`	`null`	no
nat_eip_aws_shield_protection_enabled	Enable or disable AWS Shield Advanced protection for NAT EIPs. If set to 'true', a subscription to AWS Shield Advanced must exist in this account.	`bool`	`false`	no
nat_gateway_enabled	Flag to enable/disable NAT gateways	`bool`	`true`	no
nat_gateway_public_subnet_indices	Indices (0-based) of public subnets where NAT Gateways should be placed. Use this for index-based NAT Gateway placement (e.g., [0, 1] to place NATs in first 2 public subnets per AZ). Conflicts with `nat_gateway_public_subnet_names`. If both are null, NAT Gateways are placed in all public subnets by default.	`list(number)`	`null`	no
nat_gateway_public_subnet_names	Names of public subnets where NAT Gateways should be placed. Use this for name-based NAT Gateway placement (e.g., ["loadbalancer"] to place NATs only in "loadbalancer" subnets). Conflicts with `nat_gateway_public_subnet_indices`. If both are null, NAT Gateways are placed in all public subnets by default.	`list(string)`	`null`	no
nat_instance_ami_id	A list optionally containing the ID of the AMI to use for the NAT instance. If the list is empty (the default), the latest official AWS NAT instance AMI will be used. NOTE: The Official NAT instance AMI is being phased out and does not support NAT64. Use of a NAT gateway is recommended instead.	`list(string)`	`[]`	no
nat_instance_enabled	Flag to enable/disable NAT instances	`bool`	`false`	no
nat_instance_type	NAT Instance type	`string`	`"t3.micro"`	no
private_subnets_per_az_count	The number of private subnets to provision per Availability Zone. If null, defaults to the value of `subnets_per_az_count` for backward compatibility. Use this to create different numbers of private and public subnets per AZ.	`number`	`null`	no
private_subnets_per_az_names	The names of private subnets to provision per Availability Zone. If null, defaults to the value of `subnets_per_az_names` for backward compatibility. Use this to create different named private subnets than public subnets.	`list(string)`	`null`	no
public_subnets_enabled	If false, do not create public subnets. Since NAT gateways and instances must be created in public subnets, these will also not be created when `false`.	`bool`	`true`	no
public_subnets_per_az_count	The number of public subnets to provision per Availability Zone. If null, defaults to the value of `subnets_per_az_count` for backward compatibility. Use this to create different numbers of public and private subnets per AZ.	`number`	`null`	no
public_subnets_per_az_names	The names of public subnets to provision per Availability Zone. If null, defaults to the value of `subnets_per_az_names` for backward compatibility. Use this to create different named public subnets than private subnets.	`list(string)`	`null`	no
regex_replace_chars	Terraform regular expression (regex) string. Characters matching the regex will be removed from the ID elements. If not set, `"/[^a-zA-Z0-9-]/"` is used to remove all characters other than hyphens, letters and digits.	`string`	`null`	no
region	AWS Region	`string`	n/a	yes
stage	ID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'	`string`	`null`	no
subnet_type_tag_key	Key for subnet type tag to provide information about the type of subnets, e.g. `cpco/subnet/type=private` or `cpcp/subnet/type=public`	`string`	n/a	yes
subnets_per_az_count	The number of subnet of each type (public or private) to provision per Availability Zone.	`number`	`1`	no
subnets_per_az_names	The subnet names of each type (public or private) to provision per Availability Zone. This variable is optional. If a list of names is provided, the list items will be used as keys in the outputs `named_private_subnets_map`, `named_public_subnets_map`, `named_private_route_table_ids_map` and `named_public_route_table_ids_map`	`list(string)`	[ "common" ]	no
tags	Additional tags (e.g. `{'BusinessUnit': 'XYZ'}`). Neither the tag keys nor the tag values will be modified by this module.	`map(string)`	`{}`	no
tenant	ID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is for	`string`	`null`	no
vpc_flow_logs_bucket_component_name	The name of the VPC flow logs bucket component	`string`	`"vpc-flow-logs-bucket"`	no
vpc_flow_logs_bucket_environment_name	The name of the environment where the VPC Flow Logs bucket is provisioned	`string`	`""`	no
vpc_flow_logs_bucket_stage_name	The stage (account) name where the VPC Flow Logs bucket is provisioned	`string`	`""`	no
vpc_flow_logs_bucket_tenant_name	The name of the tenant where the VPC Flow Logs bucket is provisioned. If the `tenant` label is not used, leave this as `null`.	`string`	`null`	no
vpc_flow_logs_destination_options_file_format	VPC Flow Logs file format	`string`	`"parquet"`	no
vpc_flow_logs_destination_options_hive_compatible_partitions	Flag to enable/disable VPC Flow Logs hive compatible partitions	`bool`	`false`	no
vpc_flow_logs_destination_options_per_hour_partition	Flag to enable/disable VPC Flow Logs per hour partition	`bool`	`false`	no
vpc_flow_logs_enabled	Enable or disable the VPC Flow Logs	`bool`	`true`	no
vpc_flow_logs_log_destination_type	The type of the logging destination. Valid values: `cloud-watch-logs`, `s3`	`string`	`"s3"`	no
vpc_flow_logs_traffic_type	The type of traffic to capture. Valid values: `ACCEPT`, `REJECT`, `ALL`	`string`	`"ALL"`	no

Outputs

Name	Description
availability_zone_ids	List of Availability Zones IDs where subnets were created, when available
availability_zones	List of Availability Zones where subnets were created
az_private_route_table_ids_map	Map of AZ names to list of private route table IDs in the AZs
az_private_subnets_map	Map of AZ names to list of private subnet IDs in the AZs
az_public_route_table_ids_map	Map of AZ names to list of public route table IDs in the AZs
az_public_subnets_map	Map of AZ names to list of public subnet IDs in the AZs
flow_log_destination	Destination bucket for VPC flow logs
flow_log_id	ID of the VPC flow log
gateway_vpc_endpoints	Map of Gateway VPC Endpoints in this VPC, keyed by service (e.g. "s3").
igw_id	The ID of the Internet Gateway
interface_vpc_endpoints	Map of Interface VPC Endpoints in this VPC.
max_subnet_count	Maximum allowed number of subnets before all subnet CIDRs need to be recomputed
named_private_subnets_stats_map	Map of subnet names (specified in `private_subnets_per_az_names` or `subnets_per_az_names` variable) to lists of objects with each object having four items: AZ, private subnet ID, private route table ID, NAT Gateway ID (the NAT Gateway that this private subnet routes to for egress)
named_public_subnets_stats_map	Map of subnet names (specified in `public_subnets_per_az_names` or `subnets_per_az_names` variable) to lists of objects with each object having four items: AZ, public subnet ID, public route table ID, NAT Gateway ID (the NAT Gateway in this public subnet, if any)
named_route_tables	Map of route table IDs, keyed by subnets_per_az_names. If subnets_per_az_names is not set, items are grouped by key 'common'
named_subnets	Map of subnets IDs, keyed by subnets_per_az_names. If subnets_per_az_names is not set, items are grouped by key 'common'
nat_eip_allocation_ids	Elastic IP allocations in use by NAT
nat_eip_protections	List of AWS Shield Advanced Protections for NAT Elastic IPs.
nat_gateway_ids	NAT Gateway IDs
nat_gateway_public_ips	NAT Gateway public IPs
nat_instance_ami_id	ID of AMI used by NAT instance
nat_instance_ids	NAT Instance IDs
nat_ips	Elastic IP Addresses in use by NAT
private_network_acl_id	ID of the Network ACL created for private subnets
private_route_table_ids	Private subnet route table IDs
private_subnet_arns	Private subnet ARNs
private_subnet_cidrs	Private subnet CIDRs
private_subnet_ids	Private subnet IDs
private_subnet_ipv6_cidrs	Private subnet IPv6 CIDR blocks
public_network_acl_id	ID of the Network ACL created for public subnets
public_route_table_ids	Public subnet route table IDs
public_subnet_arns	Public subnet ARNs
public_subnet_cidrs	Public subnet CIDRs
public_subnet_ids	Public subnet IDs
public_subnet_ipv6_cidrs	Public subnet IPv6 CIDR blocks
route_tables	Route tables info map
subnets	Subnets info map
vpc	VPC info map
vpc_cidr	VPC CIDR
vpc_default_network_acl_id	The ID of the network ACL created by default on VPC creation
vpc_default_security_group_id	The ID of the security group created by default on VPC creation
vpc_endpoint_dynamodb_id	ID of the DynamoDB gateway endpoint
vpc_endpoint_dynamodb_prefix_list_id	Prefix list ID for DynamoDB gateway endpoint
vpc_endpoint_interface_security_group_id	Security group ID for interface VPC endpoints
vpc_endpoint_s3_id	ID of the S3 gateway endpoint
vpc_endpoint_s3_prefix_list_id	Prefix list ID for S3 gateway endpoint
vpc_id	VPC ID

Check out these related projects.

Cloud Posse Terraform Modules - Our collection of reusable Terraform modules used by our reference architectures.
Atmos - Atmos is like docker-compose but for your infrastructure
terraform-aws-vpc - Terraform module for provisioning VPCs with advanced features
terraform-aws-dynamic-subnets - Terraform module for creating dynamic subnets with flexible configuration
AWS VPC Documentation - Official AWS VPC documentation
AWS NAT Gateway Pricing - AWS NAT Gateway pricing for cost optimization planning

References

For additional context, refer to some of these links.

cloudposse-terraform-components - Cloud Posse's upstream component
terraform-aws-vpc - CloudPosse VPC Module v3.0.0
terraform-aws-dynamic-subnets - CloudPosse Dynamic Subnets Module v3.1.0 - Enhanced subnet configuration with separate public/private control
terraform-aws-dynamic-subnets v3.1.0 Release - Adds nat_gateway_private_ips output for NAT Gateway private IP addresses

Tip

Use Terraform Reference Architectures for AWS

Use Cloud Posse's ready-to-go terraform architecture blueprints for AWS to get up and running quickly.

✅ We build it together with your team.
✅ Your team owns everything.
✅ 100% Open Source and backed by fanatical support.

📚 Learn More

Cloud Posse is the leading DevOps Accelerator for funded startups and enterprises.

Your team can operate like a pro today.

Ensure that your team succeeds by using Cloud Posse's proven process and turnkey blueprints. Plus, we stick around until you succeed.

Day-0: Your Foundation for Success

Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
Deployment Strategy. Adopt a proven deployment strategy with GitHub Actions, enabling automated, repeatable, and reliable software releases.
Site Reliability Engineering. Gain total visibility into your applications and services with Datadog, ensuring high availability and performance.
Security Baseline. Establish a secure environment from the start, with built-in governance, accountability, and comprehensive audit logs, safeguarding your operations.
GitOps. Empower your team to manage infrastructure changes confidently and efficiently through Pull Requests, leveraging the full power of GitHub Actions.

Day-2: Your Operational Mastery

Training. Equip your team with the knowledge and skills to confidently manage the infrastructure, ensuring long-term success and self-sufficiency.
Support. Benefit from a seamless communication over Slack with our experts, ensuring you have the support you need, whenever you need it.
Troubleshooting. Access expert assistance to quickly resolve any operational challenges, minimizing downtime and maintaining business continuity.
Code Reviews. Enhance your team’s code quality with our expert feedback, fostering continuous improvement and collaboration.
Bug Fixes. Rely on our team to troubleshoot and resolve any issues, ensuring your systems run smoothly.
Migration Assistance. Accelerate your migration process with our dedicated support, minimizing disruption and speeding up time-to-value.
Customer Workshops. Engage with our team in weekly workshops, gaining insights and strategies to continuously improve and innovate.

✨ Contributing

This project is under active development, and we encourage contributions from our community.

Many thanks to our outstanding contributors:

For 🐛 bug reports & feature requests, please use the issue tracker.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

Review our Code of Conduct and Contributor Guidelines.
Fork the repo on GitHub
Clone the project to your own machine
Commit changes to your own branch
Push your work back up to your fork
Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

Running Terraform Tests

We use Atmos to streamline how Terraform tests are run. It centralizes configuration and wraps common test workflows with easy-to-use commands.

All tests are located in the test/ folder.

Under the hood, tests are powered by Terratest together with our internal Test Helpers library, providing robust infrastructure validation.

Setup dependencies:

Install Atmos (installation guide)
Install Go 1.24+ or newer
Install Terraform or OpenTofu

To run tests:

Run all tests:
```
atmos test run
```
Clean up test artifacts:
```
atmos test clean
```
Explore additional test options:
```
atmos test --help
```

The configuration for test commands is centrally managed. To review what's being imported, see the atmos.yaml file.

Learn more about our automated testing in our documentation or implementing custom commands with atmos.

🌎 Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

Sign up for our newsletter and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know. Dropped straight into your Inbox every week — and usually a 5-minute read.

📆 Office Hours

Join us every Wednesday via Zoom for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a live Q&A that you can’t find anywhere else. It's FREE for everyone!

License

Preamble to the Apache License, Version 2.0

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.