Customers using PrivateLink (AWS/Azure) or Private Service Connect (GCP) can now set up a custom hostname
for their private connection — a stable, readable hostname in our
*.in.cloudamqp.com
domain.
Example:
my-cluster-vpce-abc123.in.cloudamqp.com
Previously, private connections were made using either the internal IP of the endpoint or an auto-generated DNS string from the cloud provider. The new hostname keeps all traffic on the private network, and because it lives under cloudamqp.com it's covered by our TLS certificate — so hostname verification works out of the box. It's also easier to reference in application code and matches the format of our public hostnames.
Available today for all plans with PrivateLink or Private Service Connect.
