Accessing resources in another VPC using Amazon Route 53 and AWS PrivateLink
I'm trying to access resources (such as an LDAP server) in a VPC in another AWS account. In the second account, an AWS PrivateLink endpoint service is being used to expose the LDAP server. I need to connect to this LDAP server using TLS and I want to create the correct DNS entry. What's the best way to do this?
AWS PrivateLink now supports private DNS names for internal and 3rd party services. According to this What's New update:
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.
Relevant questions
AWS Organization Migration from one Account to another account, resources are not visible
asked 2 months agoCopy data from EFS to EFS in another AWS account.
asked 2 years agoSeeding of a Elasticache cluster in another account in another region
asked 3 months agoDoes moving domain hosted in Route 53 from one account to another also move dependent resources?
Accepted Answerasked 4 years agoAWS Lightsail - Accessing a mysql database in a different account?
asked 2 years agoAccessing a RDS database in another account using AWS PrivateLink
Accepted Answerasked 4 years agoAccessing RDS in Private Isolated VPC using IAM Authentication
asked 6 months agoConnect Lightsail instance to AWS instance in a private subnet
asked 4 months agoAccessing resources in another VPC using Amazon Route 53 and AWS PrivateLink
Accepted Answerasked 2 years agoAWS WAF - protecting resources in another account
Accepted Answerasked 7 months ago