This article introduces how to create the private hosted zone in AWS Route 53 for EDB Postgres AI Cloud Service clusters. It applies to 3 scenarios:
-
The connection string for private endpoint connections to BYOA clusters will be updated. It's not possible to validate TLS certificates using the verify-full option. When using a private hosted zone, you can configure a DNS entry for the original hostname of your cluster.
-
When you want to consistently use the same connection string to connect with the different EDB Cloud Clusters.
-
When you want to set up a custom domain for the EDB Cloud Clusters.
Create a private hosted zone
- Go to AWS
Route 53(Global) -Hosted Zones(this service is global) - Add a
Private Hosted zones - With domain info:
private.0pzrbsrodkp2py7f.biganimal.io
You can set this step with your preferred domain, but the new server hostname may not be able to be validated by TLS certificates using verify-full. - Choose your client VPCs and create the zone
Create Record
Scenario 1 Connection with AWS Private Endpoint
You can connect EDB Cloud Database cluster with your AWS private endpoint.
Scenario 2 Connection Without AWS Private Endpoint in the same AWS Account
If a private endpoint is not used, you can set the alias to the network load balancer. However, this requires all the settings to be in the same AWS account.