Hello Yunxi, When creating a Virtual Private Cloud (VPC) endpoint within an AWS account, AWS automatically assigns a DNS name as part of the endpoint creation process, The New Assigned DNS name Resolve the Private IP address of the Endpoint. The AWS-assigned DNS remains consistent. Incase you need to customise this name for Different VPC that is possible by using the Private Hosted Zones (PHZ). Each PHZ can have an Record that can resolve the Endpoint Private IP (Use Alias), then PHZ can be linked to Other Account VPCs (I am assuming that these accounts having rechability).
The VPC endpoint has its independent control policy, that can be used to enable a specification of who can use this Endpoint. This granular control is implemented through attaching Endpoint Policy.
- AWS OFFICIALUpdated 9 months ago
- How can I use an Amazon VPC endpoint to activate a DataSync agent across AWS Regions or across accounts?AWS OFFICIALUpdated 8 days ago
- How do I troubleshoot issues with hosted zones in Route 53 that have the same domain names in different AWS accounts?AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- EXPERTpublished 4 months ago