cloudposse/vpc
Terraform module that defines a VPC with public/private subnets across multiple AZs.
About
Terraform module that defines a VPC with public/private subnets across multiple AZs.
Maintained by cloudposse on the Terraform Registry. Latest version 3.0.0, 5.2M downloads. Requires providers: aws >= 4.9.0.
Deploy creates a StackGuardian workflow from the module's GitHub repository, pinned to this version. You set the inputs, see the plan, then approve the apply.
Use cases
- Landing-zone networking: one module, one approved pattern per team.
- Shared VPC or hub-and-spoke for several accounts or projects.
- Ephemeral environments that need their own network each time.
Inputs
No required inputs. Every variable has a default, so the first run works with an empty input form.
36 inputs, 16 outputs in total. The full list, with defaults and descriptions, is on the registry page.
What it creates
aws_vpcaws_internet_gatewayaws_egress_only_internet_gatewayaws_default_security_groupaws_default_route_tableaws_default_network_aclaws_vpc_ipv4_cidr_block_associationaws_vpc_ipv6_cidr_block_association
How it runs on StackGuardian
Terraform workflow from the module's GitHub repository: plan, policy check, approval, then apply.
Approvals happen in StackGuardian. An agent can never approve its own run. Every run keeps its plan, policy results and approver in the audit log.