By default, there is no way that resources hosted in a private subnet can access the internet. NAT is a way to achieve that. However, any resource outside the VPC can't access the resources in a private subnet. We can use a NAT instance or a NAT Gateway to achieve this. However NAT Gateway is a scalable, managed service that does not require any administration. In this section, we will see how to manage a NAT Gateway.
Managing a NAT Gateway
Getting ready
We need to have an AWS account created with a user that has permissions to manage the NAT which we already have. We need to create an Elastic IP to be attached to with NAT, which is provided here. We shall learn details about Elastic IPs in the later sections.
...
