dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix: misleading privatelink dns copy (#50771)

Browse Source 
Somewhat urgent update to documentation based on new AWS behavior.
Will include additional details when we properly support custom DNS for
privatelink

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated the PrivateLink endpoint creation guide’s Option A steps and
numbering. The DNS record note now stands on its own, without
referencing a removed step.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
This commit is contained in:
Stephen Morgan authored and GitHub committed 2026-09-22 21:55:26 -07:00
1 parent cd77bebafd
commit e7e76ca0da
1 file changed
+6 -7
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/guides/platform/privatelink.mdx
+6 -7
View File
@@ -100,16 +100,15 @@ In your AWS account, you have two options to establish connectivity:
- The resource configuration name will be in the format `[organisation]-[project-ref]-rc`
- If you have multiple connections, match the **Resource configuration ID** shown for that connection in **View connection** to confirm you select the configuration for the correct database
7. Select your VPC from the dropdown. This should match the VPC you selected for your security group in Step 3
8. Enable the **Enable DNS name** option if you want to use a DNS record instead of the endpoints IP address(es)
9. Choose the appropriate subnets for your network
8. Choose the appropriate subnets for your network
- AWS will provision a private ENI for you in each selected subnet
- IP address type should be set to IPv4
10. Choose the security group you created in Step 3.
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:
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:
- 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 it in step 8
- The DNS record will be in the **Associations** section of the endpoint details in the **DNS Name** field
#### Option B: Attach resource configuration to an existing VPC lattice service network