How can I set up my VPC endpoint service to use a custom private DNS name?
I'm a service provider. I created a virtual private cloud (VPC) endpoint service (AWS PrivateLink) in my Amazon Virtual Private Cloud (Amazon VPC). How can I confirm that consumers of my service can access my VPC endpoint using a custom private domain name system (DNS) name?
Service providers can specify a private DNS name for a new or existing endpoint service. To use a private DNS name, you need to turn on the feature and then specify a private DNS name. Before your service consumers can use the private DNS name, you must verify that you control the domain or subdomain. You can initiate domain ownership verification using the Amazon VPC console or API. After the domain ownership verification is complete, consumers can access the endpoint using the private DNS name.
Create the VPC interface endpoints in the VPC of your service consumer account using the service name provided by the service provider. You can't turn on private DNS names until the endpoint connection request is accepted by the service provider. Note: If your service provider doesn't require their acceptance, you can turn on private DNS names and then skip the following steps.
Contact the service provider to request their acceptance of the connection request. See Accept or reject connection requests. Note: After an interface endpoint is accepted, it is in the "Available" state. You can verify the endpoint's acceptance by referring to the "Status" of the VPC interface endpoint in your service consumer account.