Create a NAT Gateway with Amazon Console: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 15: Line 15:
{{Internal|Amazon_VPC_Concepts#NAT_Gateway|NAT Gateway}}
{{Internal|Amazon_VPC_Concepts#NAT_Gateway|NAT Gateway}}


<font color=darkgray>TODO - document this</font) and then a route to them needs to be added to the corresponding routing tables (<font color=darkgray>TODO - document this https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html#nat-gateway-create-route</font).
Pick an unused Elastic IP or create a new one.
 
Once the NAT gateway is created, add a route to it from the subnet that needs outbound access. In the subnet's route table: Add Route -> Destination: 0.0.0.0/0, Target: the NAT that has just been created.

Latest revision as of 05:12, 9 April 2019

External

Internal

Procedure

  • Amazon VPC -> NAT Gateways -> Create NAT Gateway.

Subnet: must be a public subnet, which will provide routing for the NAT's elastic IP address. For reasons, see:

NAT Gateway

Pick an unused Elastic IP or create a new one.

Once the NAT gateway is created, add a route to it from the subnet that needs outbound access. In the subnet's route table: Add Route -> Destination: 0.0.0.0/0, Target: the NAT that has just been created.