{"id":23915,"date":"2015-07-28T15:55:31","date_gmt":"2015-07-28T10:25:31","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=23915"},"modified":"2015-07-29T11:38:24","modified_gmt":"2015-07-29T06:08:24","slug":"configure-nat-instance-on-aws","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/configure-nat-instance-on-aws\/","title":{"rendered":"Configure NAT Instance on AWS"},"content":{"rendered":"

The purpose of this blog post is to configure NAT (network address translation) instance on AWS by setting up customized Virtual Private Cloud (VPC) . AWS EC2 Instances<\/a> that we have\u00a0launched into a private sub-nets in a VPC can’t communicate with the Internet. So we use\u00a0NAT instance launched in our public sub-net in our\u00a0VPC to enable instances in the private sub-nets to initiate outbound traffic to the Internet, but prevent the instances from receiving inbound traffic by someone on the Internet for security reasons.NAT is a methodology of remapping one IP address into another by modifying network address information in internet protocol data-gram packet headers while they are in transit across a traffic routing device.<\/p>\n

NAT is the process where a network device, usually a firewall, assigns a public address to a server\u00a0(or group of servers) inside a private network. The main use of NAT is to limit the number of public IP addresses for both economy and security purposes.<\/p>\n

Brief Overview to configure NAT instance on AWS ::<\/strong><\/p>\n