A company wants to use NAT gateways in its AWS environment. The company's Amazon EC2 instances in private subnets must be able to connect to the public internet through the NAT gateways.
Which solution will meet these requirements?
A.
Create public NAT gateways in the same private subnets as the EC2 instances.
B.
Create private NAT gateways in the same private subnets as the EC2 instances.
C.
Create public NAT gateways in public subnets in the same VPCs as the EC2 instances.
D.
Create private NAT gateways in public subnets in the same VPCs as the EC2 instances.
I think the correct is C, because D would require more than just private NAT gateway.
Private – Instances in private subnets can connect to other VPCs or your on-premises network through a private NAT gateway. You can route traffic from the NAT gateway through a transit gateway or a virtual private gateway. You cannot associate an elastic IP address with a private NAT gateway. You can attach an internet gateway to a VPC with a private NAT gateway, but if you route traffic from the private NAT gateway to the internet gateway, the internet gateway drops the traffic.
https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
anikolov
Highly Voted 8 months, 2 weeks agomestule
Highly Voted 8 months, 3 weeks agoKezuko
Most Recent 7 months, 1 week agoknben
8 months agoAndy_09
8 months, 3 weeks ago