terraform-aws-dynamic-subnets

Terraform module to provision public and private subnets in an existing VPC

Note: this module is intended for use with an existing VPC and existing Internet Gateway. To create a new VPC, use terraform-aws-vpc module.

---

This project is part of our comprehensive "SweetOps" approach towards DevOps.

It's 100% Open Source and licensed under the APACHE2.

We literally have hundreds of terraform modules that are Open Source and well-maintained. Check them out!

Usage

IMPORTANT: The master branch is used in source just as an example. In your code, do not pin to master because there may be breaking changes between releases. Instead pin to the release tag (e.g. ?ref=tags/x.y.z) of one of our latest releases.

module "subnets" {
  source              = "git::https://github.com/cloudposse/terraform-aws-dynamic-subnets.git?ref=master"
  namespace           = "eg"
  stage               = "prod"
  name                = "app"
  vpc_id              = "vpc-XXXXXXXX"
  igw_id              = "igw-XXXXXXXX"
  cidr_block          = "10.0.0.0/16"
  availability_zones  = ["us-east-1a", "us-east-1b"]
}

Learn about using providers with terraform modules.

Subnet calculation logic

terraform-aws-dynamic-subnets creates a set of subnets based on ${var.cidr_block} input and number of Availability Zones in the region.

For subnet set calculation, the module uses Terraform interpolation

cidrsubnet.

${
  cidrsubnet(
  signum(length(var.cidr_block)) == 1 ?
  var.cidr_block : data.aws_vpc.default.cidr_block,
  ceil(log(length(data.aws_availability_zones.available.names) * 2, 2)),
  count.index)
}

1. Use ${var.cidr_block} input (if specified) or use a VPC CIDR block data.aws_vpc.default.cidr_block (e.g. 10.0.0.0/16)

2. Get number of available AZ in the region (e.g. length(data.aws_availability_zones.available.names))

3. Calculate newbits. newbits number specifies how many subnets be the CIDR block (input or VPC) will be divided into. newbits is the number of binary digits.

   Example:

   newbits = 1 - 2 subnets are available (1 binary digit allows to count up to 2)

   newbits = 2 - 4 subnets are available (2 binary digits allows to count up to 4)

   newbits = 3 - 8 subnets are available (3 binary digits allows to count up to 8)

   etc.

   1. We know, that we have 6 AZs in a us-east-1 region (see step 2).

   2. We need to create 1 public subnet and 1 private subnet in each AZ, thus we need to create 12 subnets in total (6 AZs * (1 public + 1 private)).

   3. We need 4 binary digits for that ( 2⁴ = 16 ). In order to calculate the number of binary digits we should use logarithm function. We should use base 2 logarithm because decimal numbers can be calculated as powers of binary number. See Wiki for more details

      Example:

      For 12 subnets we need 3.58 binary digits (log₂12)

      For 16 subnets we need 4 binary digits (log₂16)

      For 7 subnets we need 2.81 binary digits (log₂7)

      etc.

   4. We can't use fractional values to calculate the number of binary digits. We can't round it down because smaller number of binary digits is insufficient to represent the required subnets. We round it up. See ceil.

      Example:

      For 12 subnets we need 4 binary digits (ceil(log₂12))

      For 16 subnets we need 4 binary digits (ceil(log₂16))

      For 7 subnets we need 3 binary digits (ceil(log₂7))

      etc.

   5. Assign private subnets according to AZ number (we're using count.index for that).

   6. Assign public subnets according to AZ number but with a shift according to the number of AZs in the region (see step 2)

Makefile Targets

Available targets:

  help                                Help screen
  help/all                            Display help for all targets
  help/short                          This help short screen
  lint                                Lint terraform code

Requirements

Name	Version
terraform	>= 0.12.0, < 0.14.0
aws	~> 2.0
local	~> 1.2
null	~> 2.0
template	~> 2.0

Providers

Name	Version
aws	~> 2.0

Inputs

Name	Description	Type	Default	Required
additional_tag_map	Additional tags for appending to each tag map	map(string)	{}	no
attributes	Any extra attributes for naming these resources	list(string)	[]	no
availability_zones	List of Availability Zones where subnets will be created	list(string)	n/a	yes
aws_route_create_timeout	Time to wait for AWS route creation specifed as a Go Duration, e.g. 2m	string	"2m"	no
aws_route_delete_timeout	Time to wait for AWS route deletion specifed as a Go Duration, e.g. 5m	string	"5m"	no
cidr_block	Base CIDR block which will be divided into subnet CIDR blocks (e.g. 10.0.0.0/16)	string	n/a	yes
context	Default context to use for passing state between label invocations	object({ namespace = string environment = string stage = string name = string enabled = bool delimiter = string attributes = list(string) label_order = list(string) tags = map(string) additional_tag_map = map(string) regex_replace_chars = string })	{ "additional_tag_map": {}, "attributes": [], "delimiter": "", "enabled": true, "environment": "", "label_order": [], "name": "", "namespace": "", "regex_replace_chars": "", "stage": "", "tags": {} }	no
delimiter	Delimiter to be used between namespace, stage, name and attributes	string	"-"	no
enabled	Set to false to prevent the module from creating any resources	bool	true	no
environment	The environment name if not using stage	string	""	no
existing_nat_ips	Existing Elastic IPs to attach to the NAT Gateway or Instance instead of creating a new one.	list(string)	[]	no
igw_id	Internet Gateway ID the public route table will point to (e.g. igw-9c26a123)	string	n/a	yes
label_order	The naming order of the ID output and Name tag	list(string)	[]	no
map_public_ip_on_launch	Instances launched into a public subnet should be assigned a public IP address	bool	true	no
max_subnet_count	Sets the maximum amount of subnets to deploy. 0 will deploy a subnet for every provided availablility zone (in availability_zones variable) within the region	number	0	no
name	Solution name, e.g. 'app' or 'cluster'	string	""	no
namespace	Namespace, which could be your organization name or abbreviation, e.g. 'eg' or 'cp'	string	""	no
nat_gateway_enabled	Flag to enable/disable NAT Gateways to allow servers in the private subnets to access the Internet	bool	true	no
nat_instance_enabled	Flag to enable/disable NAT Instances to allow servers in the private subnets to access the Internet	bool	false	no
nat_instance_type	NAT Instance type	string	"t3.micro"	no
private_network_acl_id	Network ACL ID that will be added to private subnets. If empty, a new ACL will be created	string	""	no
private_subnets_additional_tags	Additional tags to be added to private subnets	map(string)	{}	no
public_network_acl_id	Network ACL ID that will be added to public subnets. If empty, a new ACL will be created	string	""	no
public_subnets_additional_tags	Additional tags to be added to public subnets	map(string)	{}	no
regex_replace_chars	Regex to replace chars with empty string in namespace, environment, stage and name. By default only hyphens, letters and digits are allowed, all other chars are removed	string	"/[^a-zA-Z0-9-]/"	no
stage	Stage, e.g. 'prod', 'staging', 'dev', or 'test'	string	""	no
subnet_type_tag_key	Key for subnet type tag to provide information about the type of subnets, e.g. cpco.io/subnet/type=private or cpco.io/subnet/type=public	string	"cpco.io/subnet/type"	no
subnet_type_tag_value_format	This is using the format interpolation symbols to allow the value of the subnet_type_tag_key to be modified.	string	"%s"	no
tags	Additional tags to apply to all resources that use this label module	map(string)	{}	no
vpc_default_route_table_id	Default route table for public subnets. If not set, will be created. (e.g. rtb-f4f0ce12)	string	""	no
vpc_id	VPC ID where subnets will be created (e.g. vpc-aceb2723)	string	n/a	yes

Outputs

Name	Description
availability_zones	List of Availability Zones where subnets were created
nat_gateway_ids	IDs of the NAT Gateways created
nat_gateway_public_ips	EIP of the NAT Gateway
nat_instance_ids	IDs of the NAT Instances created
nat_ips	IP Addresses in use for NAT
private_route_table_ids	IDs of the created private route tables
private_subnet_cidrs	CIDR blocks of the created private subnets
private_subnet_ids	IDs of the created private subnets
public_route_table_ids	IDs of the created public route tables
public_subnet_cidrs	CIDR blocks of the created public subnets
public_subnet_ids	IDs of the created public subnets

Share the Love

Like this project? Please give it a ★ on our GitHub! (it helps us a lot)

Are you using this project or any of our other projects? Consider leaving a testimonial. =)

Related Projects

Check out these related projects.

• terraform-aws-vpc - Terraform Module that defines a VPC with public/private subnets across multiple AZs with Internet Gateways
• terraform-aws-vpc-peering - Terraform module to create a peering connection between two VPCs
• terraform-aws-kops-vpc-peering - Terraform module to create a peering connection between a backing services VPC and a VPC created by Kops
• terraform-aws-named-subnets - Terraform module for named subnets provisioning.

Help

Got a question? We got answers.

File a GitHub issue, send us an email or join our Slack Community.

DevOps Accelerator for Startups

We are a DevOps Accelerator. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.

Work directly with our team of DevOps experts via email, slack, and video conferencing.

We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.

• Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
• Release Engineering. You'll have end-to-end CI/CD with unlimited staging environments.
• Site Reliability Engineering. You'll have total visibility into your apps and microservices.
• Security Baseline. You'll have built-in governance with accountability and audit logs for all changes.
• GitOps. You'll be able to operate your infrastructure via Pull Requests.
• Training. You'll receive hands-on training so your team can operate what we build.
• Questions. You'll have a direct line of communication between our teams via a Shared Slack channel.
• Troubleshooting. You'll get help to triage when things aren't working.
• Code Reviews. You'll receive constructive feedback on Pull Requests.
• Bug Fixes. We'll rapidly work with you to fix any bugs in our projects.

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.

Discourse Forums

Participate in our Discourse Forums. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.

Newsletter

Sign up for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.

Office Hours

Join us every Wednesday via Zoom for our weekly "Lunch & Learn" sessions. It's FREE for everyone!

Contributing

Bug Reports & Feature Requests

Please use the issue tracker to report any bugs or file feature requests.

Developing

If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.

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

1. Fork the repo on GitHub
2. Clone the project to your own machine
3. Commit changes to your own branch
4. Push your work back up to your fork
5. 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!

Copyright

Copyright © 2017-2020 Cloud Posse, LLC

License

See LICENSE for full details.

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.

About

This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know by leaving a testimonial!

We're a DevOps Professional Services company based in Los Angeles, CA. We ❤️ Open Source Software.

We offer paid support on all of our projects.

Check out our other projects, follow us on twitter, apply for a job, or hire us to help with your cloud strategy and implementation.

Contributors

Erik Osterman	Andriy Knysh	Sergey Vasilyev	Vladimir	Konstantin B	dcowan-vestmark	Ivan Pinatti	Oscar Sullivan