AWS PrivateLink now supports Private DNS names for internal and 3rd party services
You can now access AWS PrivateLink based services privately from within your VPC using Private DNS names like ‘myinternalservice.mycompany.com’. With this announcement, you can access your internal / 3rd party AWS PrivateLink based services, without making changes in your application to use the AWS specified public DNS Name or managing private DNS Names your own Route 53 Private Hosted Zones.
You can now access AWS PrivateLink based services privately from within your VPC using Private DNS names like ‘myinternalservice.mycompany.com’. With this announcement, you can access your internal / 3rd party AWS PrivateLink based services, without making changes in your application to use the AWS specified public DNS Name or managing private DNS Names your own Route 53 Private Hosted Zones.
To get started, you need to specify the Private DNS Name during service configuration and confirm ownership of the public domain that corresponds to the DNS name that you want consumers of your service to use. Once this is done, consumers of your service can simply ‘enable Private DNS Name’ in the endpoint configuration workflow and use the DNS name specified by you.
This functionality is available in all AWS Regions except China regions. To get started, refer our documentation.