This website uses cookies to ensure you get the best experience.
Learn more.
EC2 instances in a private IPv4 subnet need outbound access to public package repositories without accepting unsolicited inbound internet connections. The VPC has an internet gateway. Which configuration is required for a public NAT gateway solution? Select 2 answers.
Published
- Add a default IPv4 route from the private subnet directly to the internet gateway and keep every instance without a public IPv4 address.
- Create a public NAT gateway with an Elastic IP in a public subnet whose route table directs internet traffic to the internet gateway.
- Use an egress-only internet gateway to translate private IPv4 addresses.
- Add a default IPv4 route from the private subnet route table to the NAT gateway.
- Allow unsolicited inbound connections by adding port-forwarding rules to the NAT gateway.
Comments — 0
Sign in to comment