AnalyticDB:Enable public network access for an AnalyticDB for PostgreSQL Supabase project

Billing

For more information about EIP billing, see Billing overview.

Procedure

1. Log on to the EIP console and create an Elastic IP Address.

   Important

   The EIP and the AnalyticDB for PostgreSQL Supabase project must be in the same region. For more information about EIP configuration parameters, see Elastic IP Address.

2. Click Associate with Resource in the Actions column of the target EIP.

3. Configure the binding information.

   1. For Instance Type, select ENI.

   2. For Association Mode, select NAT Mode.

   3. Select the project to associate.

      Filter the list by the vSwitch ID of your AnalyticDB for PostgreSQL Supabase project. Then, find and select the target ENI.

      1. Click the network interface ID to open its details page.

         

      2. Hover your pointer over the tag. If the displayed ID matches the ID of your AnalyticDB for PostgreSQL Supabase project, it is the correct network interface.

         

   4. Click OK.

Verification

You can verify public network access using features like Auth, email sending, or Edge Functions. This section uses email sending as an example.

1. Log on to the Supabase Dashboard. In the sidebar, click Authentication > Users.

2. On the Users page, click Add user in the upper-right corner, and select Send invitation.

   

3. Enter a test email address and send the email. If the email is sent successfully, public network access is configured correctly.

References

Alternatively, you can enable an Internet NAT gateway for the VPC hosting your AnalyticDB for PostgreSQL instance, then create an SNAT entry for your Supabase project’s VPC or vSwitch to enable public network access. Creating an Internet NAT gateway incurs fees. For more information, see NAT Gateway billing.