A company is using AWS Elastic Disaster Recovery (AWS DRS) to replicate on-premises servers to AWS. The replication traffic is routed over an AWS Direct Connect connection to a staging area VPC that lacks internet access. The replication agents installed on the on-premises servers cannot establish communication with the AWS DRS service. Which configuration step should a SysOps Administrator take to resolve this issue while adhering to the requirement of not using the public internet?
- AAttach an Internet Gateway to the staging area VPC, and add a default route pointing to the Internet Gateway in the staging subnet's route table.
- BCreate a gateway VPC endpoint for the AWS DRS service in the staging area VPC, and associate it with the route tables of the staging subnets.
- Create interface VPC endpoints (AWS PrivateLink) for the AWS DRS service in the staging area VPC, and ensure private DNS is enabled.Answer
- DCreate interface VPC endpoints for the AWS DRS service in the staging area VPC, and configure a custom network ACL on the staging subnets that allows outbound HTTPS traffic but denies all inbound ephemeral ports.
Answer
Create interface VPC endpoints (AWS PrivateLink) for the AWS DRS service in the staging area VPC, and ensure private DNS is enabled.
Creating interface VPC endpoints (AWS PrivateLink) for the AWS DRS service in the staging area VPC provides private connectivity that does not traverse the public internet. Enabling private DNS ensures that the replication agents installed on-premises automatically resolve the standard service endpoints to the private IP addresses of the endpoints in the VPC.
Step-by-Step Solution
Key Concept
Establishing private, secure connectivity to AWS Elastic Disaster Recovery (AWS DRS) using AWS PrivateLink interface VPC endpoints over Direct Connect.