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?
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 4 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren