EC2 instances in a company's VPC were previously contacting AWS services over the public internet. The company deployed AWS PrivateLink endpoints so traffic no longer goes over the internet, but after deployment the EC2 instances lost all connectivity to the required AWS services. Which combination of actions should a network engineer take to restore access to the AWS services? (Choose two.)

When using PrivateLink, EC2 instances need to resolve the service endpoints to their private IP addresses. This requires DNS resolution within the VPC. Setting enableDnsSupport to True for the VPC and ensuring DNS is enabled for each VPC endpoint allows the instances to resolve the AWS service endpoints to their private IP addresses, enabling private connectivity. Additionally, VPC endpoint policies control which principals can access the service through the endpoint and what actions they can perform. If the policy is too restrictive, it will block communication. Adding a route to the VPC route table is incorrect because PrivateLink endpoints are automatically routed within the VPC; no explicit route table entry is needed. Creating Route 53 public or private hosted zones for every service is unnecessary and incorrect, as PrivateLink handles DNS resolution automatically within the VPC when properly configured.