Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

docs: reference the ability to use custom dns from VPCE (#51778)

Stephen Morgan09f80f528ec4
diff --git a/apps/docs/content/guides/platform/privatelink.mdx b/apps/docs/content/guides/platform/privatelink.mdx
index a23d78c5a6e..b840095b613 100644
--- a/apps/docs/content/guides/platform/privatelink.mdx
+++ b/apps/docs/content/guides/platform/privatelink.mdx
@@ -104,11 +104,16 @@ In your AWS account, you have two options to establish connectivity:
- AWS will provision a private ENI for you in each selected subnet
- IP address type should be set to IPv4
9. Choose the security group you created in Step 3.
-10. Click **Create endpoint**
-11. After creation, you will see the endpoint in the [Endpoints](https://console.aws.amazon.com/vpcconsole/home#Endpoints:) section with a status of "Available"
-12. For connectivity:
+10. Optionally, select **Enable private DNS name** to use a Supabase hostname instead of the endpoint DNS name
+ - The private DNS name is `db.[project_ref].privatelink.supabase.co`
+ - It resolves only to the endpoint from within the selected VPC
+ - Your VPC must have **DNS resolution** and **DNS hostnames** enabled
+11. Click **Create endpoint**
+12. After creation, you will see the endpoint in the [Endpoints](https://console.aws.amazon.com/vpcconsole/home#Endpoints:) section with a status of "Available"
+13. For connectivity:
- The IP addresses of the endpoint will be listed in the **Subnets** section of the endpoint details
- The DNS record will be in the **Associations** section of the endpoint details in the **DNS Name** field
+ - If you enabled a private DNS name, use `db.[project_ref].privatelink.supabase.co`
#### Option B: Attach resource configuration to an existing VPC lattice service network
@@ -160,12 +165,18 @@ postgresql://user:pass@db.[project-ref].supabase.co:5432/postgres
# After (private)
postgresql://user:[email protected]:5432/postgres
+# After (private, with private DNS name enabled)
+postgresql://user:pass@db.[project-ref].privatelink.supabase.co:5432/postgres
+
# PgBouncer connection
# Before (public)
postgresql://user:pass@db.[project-ref].supabase.co:6543/postgres
# After (private)
postgresql://user:[email protected]:6543/postgres
+
+# After (private, with private DNS name enabled)
+postgresql://user:pass@db.[project-ref].privatelink.supabase.co:6543/postgres
```
### Step 7: Restrict public database access (optional)