A SysOps Administrator is configuring Amazon EC2 instances in a private subnet with no internet access to be managed by AWS Systems Manager Session Manager. The Administrator creates the required Interface VPC Endpoints for the `ssm`, `ssmmessages`, and `ec2messages` services within the VPC. The security group for the Interface VPC Endpoints is configured to allow inbound HTTPS traffic from the EC2 instances. However, the SSM Agent on the EC2 instances fails to connect to the Systems Manager service.
Which of the following is the most likely cause of this issue?
- AThe route table associated with the private subnet is missing routes that target the Interface VPC Endpoints for the Systems Manager services.
- Private DNS hostnames are disabled for the Interface VPC Endpoints, causing the SSM Agent to attempt to resolve the default public Systems Manager endpoints instead of the private endpoints.Answer
- CThe private subnet is missing a route targeting an Internet Gateway in its route table to allow the SSM Agent to perform DNS resolution.
- DThe security group associated with the Interface VPC Endpoints does not allow outbound UDP traffic on port 53 to the VPC's AmazonProvidedDNS resolver.
Answer
Private DNS hostnames are disabled for the Interface VPC Endpoints, causing the SSM Agent to attempt to resolve the default public Systems Manager endpoints instead of the private endpoints.
Enabling Private DNS hostnames allows the default public service endpoints to resolve to the private IP addresses of the Interface VPC Endpoint's Elastic Network Interfaces (ENIs). Since the EC2 instances do not have internet access, they cannot reach the public IPs of the service endpoints. Enabling Private DNS ensures the connection remains internal and secure.
Step-by-Step Solution
Key Concept
VPC Endpoints and PrivateLink Integration