Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ #42 Add support for provisioning only a single NAT Gateway #1

Merged
merged 1 commit into from
Jul 23, 2017

Conversation

n8io
Copy link
Owner

@n8io n8io commented Jul 23, 2017

DEPENDENT ON PR terraform-community-modules#57

Sample setup:

  • You have 2 public subnets
  • You have 2 private subnets

Scenario 1 (high availability)

Prior to this change when you set enable_nat_gateway=true you would get the following infrastructure:

  • 2 EIPs (1 per private subnet)
  • 2 NAT Gateway (1 per private subnet)

While this follows high availability best practices and should be your configuration in a production, sometimes you don't want to incur the cost of having multiple NAT gateways in your dev and testing environments.

Scenario 2 (low availability)

After this change when you set enable_nat_gateway=true and single_nat_gateway=true you would get the following infrastructure:

  • 1 EIP (1 total)
  • 1 NAT Gateway (1 total)

Meaning that you share a single EIP/NAT gateway pairing across all of your private subnets. Reducing costs while maintaining functionality but being far less available. This leaves the onus on the person terraforming to decide whether or not they are ok with the cost/risk tradeoff.

Again, this scenario is not intended for a production environment.

@n8io n8io force-pushed the feature/allow-single-nat-gateway branch from 875715f to 4b91892 Compare July 23, 2017 14:15
@n8io n8io force-pushed the feature/allow-single-nat-gateway branch from 4b91892 to ed802eb Compare July 23, 2017 14:16
@n8io n8io merged commit a6fac14 into master Jul 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant