A SysOps Administrator is deploying Amazon EC2 instances in a private subnet with no internet connectivity. The instances need to send messages to Amazon SQS. The administrator creates an Interface VPC Endpoint for SQS in the VPC. However, the EC2 instances are unable to resolve the standard SQS endpoint URL (sqs.us-east-1.amazonaws.com) to the private IP addresses of the VPC endpoint. What must the administrator do to resolve this DNS resolution issue?
- Enable Private DNS names for the Interface VPC Endpoint.Cevap
- BAdd a route to the private subnet route table targeting the Amazon SQS Interface VPC Endpoint.
- CUpdate the security group of the Interface VPC Endpoint to allow inbound DNS queries on UDP port 53 from the EC2 instances.
- DCreate an Internet Gateway and attach it to the VPC to allow DNS resolution requests to reach public AWS DNS servers.
Cevap
Enable Private DNS names for the Interface VPC Endpoint.
Enabling the Private DNS option for the VPC endpoint ensures that the VPC's internal DNS resolver maps the standard public service DNS name to the private IP addresses of the endpoint's network interfaces.
Adım Adım Çözüm
Anahtar Kavram
VPC Endpoints and PrivateLink Integration