Skip to content

Commit

Permalink
Updated README. There will be one NAT gateway per AZ.
Browse files Browse the repository at this point in the history
  • Loading branch information
antonbabenko committed May 18, 2017
1 parent 2cbc513 commit af6e873
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Module Input Variables
- `azs` - list of AZs in which to distribute subnets
- `enable_dns_hostnames` - should be true if you want to use private DNS within the VPC
- `enable_dns_support` - should be true if you want to use private DNS within the VPC
- `enable_nat_gateway` - should be true if you want to provision NAT Gateways for each of your private networks
- `enable_nat_gateway` - should be true if you want to provision NAT Gateways
- `map_public_ip_on_launch` - should be false if you do not want to auto-assign public IP on launch
- `private_propagating_vgws` - list of VGWs the private route table should propagate
- `public_propagating_vgws` - list of VGWs the public route table should propagate
Expand All @@ -25,7 +25,7 @@ Module Input Variables
It's generally preferable to keep `public_subnets`, `private_subnets`, and
`azs` to lists of the same length.

This module optionally creates NAT Gateways in each public subnet and sets them
This module optionally creates NAT Gateways (one per availability zone) and sets them
as the default gateways for the corresponding private subnets.

Usage
Expand Down

0 comments on commit af6e873

Please sign in to comment.