A SysOps administrator launches an Amazon EC2 instance in a subnet that is intended to be public. However, the instance is unable to send or receive traffic from the internet. Which two configurations should the administrator verify to resolve this connectivity issue?
- Verify that the subnet's route table contains a route for pointing to the VPC's Internet Gateway (IGW).Cevap
- Verify that the EC2 instance has been assigned a public IPv4 address or an Elastic IP address.Cevap
- CVerify that a Virtual Private Gateway (VGW) is attached to the VPC and configured as the target for the route.
- DConfigure the subnet's Network Access Control List (NACL) to allow outbound traffic to on ports 80 and 443, while blocking ephemeral ports.
- ECreate an AWS Gateway VPC Endpoint for the internet and associate it with the subnet's route table.
Cevap
To resolve the connectivity issue, the administrator must verify that the subnet's route table contains a route for targeting the Internet Gateway, and verify that the EC2 instance is assigned a public IPv4 address or an Elastic IP address.
For an EC2 instance in a public subnet to communicate with the internet, the subnet's route table must route all non-local traffic () to an attached Internet Gateway, and the instance must have a public IP address (either auto-assigned or an Elastic IP) so the Internet Gateway can translate it to the private IP.
Adım Adım Çözüm
Anahtar Kavram
Basic public subnet configuration and internet routing requirements