A company's VPC has Amazon EC2 instances that are communicating with AWS services over the public internet. The company needs to change the connectivity so that the communication
does not occur over the public intemet.
The company deploys AWS PrivateLink endpoints in the VPC. After the deployment of the PrivateLink endpoints, the EC2 instances can no longer communicate at all with the required AWS
services.
Which combination of steps should a network engineer take to restore communication with the AWS services? (Select TWO.)
To use AWS PrivateLink, you need to create interface type VPC endpoints for the services that you want to access privately from your VPC1. These endpoints appear as elastic network interfaces (ENIs) with private IPs in your subnets2. To enable DNS resolution for these endpoints, you need to set the enableDnsSupport attribute to True for your VPC, and enable DNS support for each endpoint3. You also need to ensure that the VPC endpoint policy allows communication between your VPC and the service4. You do not need to create any route table entries or Route 53 hosted zones for the endpoints, as they are not required for PrivateLink5.
AWS PrivateLink FAQs -- Amazon Web Services 2: AWS PrivateLink and service endpoint - Amazon EC2 Overview and Networking Introduction for Telecom Companies 3: VPC Endpoints: Secure and Direct Access to AWS Services 4: AWS PrivateLink and service endpoint - Amazon EC2 Overview and Networking Introduction for Telecom Companies 5: AWS Private Link vs VPC Endpoint - Stack Overflow
Taryn
3 months agoNieves
3 months agoShakira
4 months agoHershel
3 months agoLong
3 months agoMaricela
3 months agoLaurena
3 months agoLouvenia
3 months agoRyan
3 months agoWinfred
3 months agoBernardine
4 months agoAshanti
4 months agoClorinda
4 months agoEvangelina
4 months agoClaudio
4 months agoCorrie
4 months agoMinna
4 months agoChaya
4 months ago