✨ #42 Add support for provisioning only a single NAT Gateway #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DEPENDENT ON PR terraform-community-modules#57
Sample setup:
Scenario 1 (high availability)
Prior to this change when you set
enable_nat_gateway=true
you would get the following infrastructure: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
andsingle_nat_gateway=true
you would get the following infrastructure: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.