Download
Terraform module which creates VPC resources on AWS. By default this module will provision new Elastic IPs for the VPC's NAT Gateways. This means that when creating a new VPC, new IPs are allocated, and when that VPC is destroyed those IPs are released. Sometimes it is handy to keep the same IPs even after the VPC is destroyed and re-created. To that end, it is possible to assign existing IPs to the NAT Gateways. This prevents the destruction of the VPC from releasing those IPs, while making it possible that a re-created VPC uses the same IPs. By default, if NAT Gateways are enabled, private subnets will be configured with routes for Internet traffic that point at the NAT Gateways configured by use of the above options. Since AWS Lambda functions allocate Elastic Network Interfaces in proportion to the traffic received, it can be useful to allocate a large private subnet for such allocations, while keeping the traffic they generate entirely internal to the VPC.
Features
- Allocate the IPs outside the VPC module declaration
- Supports three scenarios for creating NAT gateways
- One NAT Gateway per availability zone
- You can add additional tags with intra_subnet_tags as with other subnet types
- VPC Flow Log allows to capture IP traffic for a specific network interface (ENI), subnet, or entire VPC
- Public access to Redshift cluster
Project Samples
