Question $1$

An AWS Developer has launched an instance as a NAT server in a public subnet. He has updated the

route tables and added the NAT server as the target of internet bound traffic from private subnet But

while trying to make an outbound connection to Internet from an instance in the pfivate subnet, it

fails. How could this issue be resolved?

Attach an ENI to NAT instance and place it in private subnet

Attach an ENI to the instance in the private subnet and place it in public subnet

Attach an Elastic IP address to the instance in the private subnet

Disabiling the Source$/$Destination Check attribute on NAT instance