Skip to main content
Lakebase Postgres is built on object storage, but 99.99999% of reads are served from high-performance local caches
/Resilience & architecture/Private Networking

Neon Private Networking

Learn how to connect to your Neon project through AWS PrivateLink

View as Markdown

Private Networking availability

Private Networking is available on Neon's Scale plan. If you're on a different plan, you can request a trial from the Network Security page in your project's settings.

The Neon Private Networking feature enables secure connections to your Lakebase Postgres databases via AWS PrivateLink, bypassing the open internet for enhanced security.

Overview

In a standard setup, the client application connects to a Lakebase Postgres database over the open internet through the Neon proxy.

With Neon Private Networking, you can connect to your database via AWS PrivateLink instead of the open internet. In this setup, the client application connects through an AWS endpoint service (provided by Neon) to a Neon proxy instance that is not accessible from the public internet. This endpoint service is available only within the same AWS region as your client application. With Neon Private Networking, all traffic between the client application and the database stays within AWS's private network, rather than crossing the public internet.

Neon Private Networking diagram

Prerequisites

  • You must be on the Scale plan, and your user must be an Admin of the Neon organization. You'll encounter an access error if you attempt the setup from a personal Neon account or on a plan that doesn't include Private Networking.
  • Ensure that your client application is deployed on AWS in the same region as the database you plan to connect to. The Private Networking feature is available in all Neon-supported AWS regions. Both your client application and database must be in one of these regions.
  • Neon Private Networking supports both IPv4 and IPv6.
  • Install the Neon CLI. You will use it to add your VPC endpoint ID to your Neon organization. For installation instructions, see Neon CLI install and connect.

Configuration steps

To configure Neon Private Networking, perform the following steps:

  1. Create an AWS VPC endpoint

    important

    Do not enable private DNS names for the VPC endpoint until Step 3. You must add the VPC endpoint to your Neon organization first, as described in Step 2.

    Add all service names for your region

    A region can list multiple endpoint service names. When you create the endpoint, add all of the names listed for your region below (under Service settings). Neon adds service names over time as it expands capacity and updates this page, so re-check that list after a regional expansion. Adding those later additions is optional but improves capacity and reliability. Expansions are announced in the changelog.

    1. Go to the AWS VPC > Endpoints dashboard and select Create endpoint. Make sure you create the endpoint in the same VPC as your client application.

      VPC Dashboard

    2. Optionally, enter a Name tag for the endpoint (for example, My Neon Private Networking).

    3. For Type, select the Endpoint services that use NLBs and GWLBs category.

      VPC Create endpoint

    4. Under Service settings, specify the Service name. Some regions require specifying multiple service names, and service names vary by region:

      • us-east-1: Create entries, one for each of the following:
        • com.amazonaws.vpce.us-east-1.vpce-svc-01aeec2f4b558bc22
        • com.amazonaws.vpce.us-east-1.vpce-svc-01b3c73657ed9bd29
        • com.amazonaws.vpce.us-east-1.vpce-svc-02a0abd91f32f1ed7
        • com.amazonaws.vpce.us-east-1.vpce-svc-040132f4a2dc43d76
        • com.amazonaws.vpce.us-east-1.vpce-svc-0492424e0bf471d59
        • com.amazonaws.vpce.us-east-1.vpce-svc-074ac4111275eaf07
        • com.amazonaws.vpce.us-east-1.vpce-svc-07e0ce252b3a16acc
        • com.amazonaws.vpce.us-east-1.vpce-svc-0824666dc46176a87
        • com.amazonaws.vpce.us-east-1.vpce-svc-0adffb07ac0333ac0
        • com.amazonaws.vpce.us-east-1.vpce-svc-0b676a43303caf7d8
        • com.amazonaws.vpce.us-east-1.vpce-svc-0bef3dbe6e4a2df49
        • com.amazonaws.vpce.us-east-1.vpce-svc-0c4afbefbfdf6b031
        • com.amazonaws.vpce.us-east-1.vpce-svc-0d07f7f68c9a99f3b
        • com.amazonaws.vpce.us-east-1.vpce-svc-0de57c578b0e614a9
        • com.amazonaws.vpce.us-east-1.vpce-svc-0e018376e3c90bfae
        • com.amazonaws.vpce.us-east-1.vpce-svc-0f37140e9710ee3af
      • us-east-2: Create entries, one for each of the following:
        • com.amazonaws.vpce.us-east-2.vpce-svc-0056bdfba63cc6ea1
        • com.amazonaws.vpce.us-east-2.vpce-svc-010736480bcef5824
        • com.amazonaws.vpce.us-east-2.vpce-svc-0125f603817b3d7f7
        • com.amazonaws.vpce.us-east-2.vpce-svc-0234a2d750f731a18
        • com.amazonaws.vpce.us-east-2.vpce-svc-0465c21ce8ba95fb2
        • com.amazonaws.vpce.us-east-2.vpce-svc-0a59493ecf790eccf
        • com.amazonaws.vpce.us-east-2.vpce-svc-0ce57d490de78526a
        • com.amazonaws.vpce.us-east-2.vpce-svc-0d421498ff01becac
        • com.amazonaws.vpce.us-east-2.vpce-svc-0fcb5fccfc8573aa3
      • eu-central-1: Create entries, one for each of the following:
        • com.amazonaws.vpce.eu-central-1.vpce-svc-0260f9dcc9bf59e3e
        • com.amazonaws.vpce.eu-central-1.vpce-svc-04bac3120b20929cd
        • com.amazonaws.vpce.eu-central-1.vpce-svc-05554c35009a5eccb
        • com.amazonaws.vpce.eu-central-1.vpce-svc-0575a0aedec0492b8
        • com.amazonaws.vpce.eu-central-1.vpce-svc-05a252e6836f01cfd
        • com.amazonaws.vpce.eu-central-1.vpce-svc-05a5b03b56954593a
        • com.amazonaws.vpce.eu-central-1.vpce-svc-07617c7fc17794cc7
        • com.amazonaws.vpce.eu-central-1.vpce-svc-0fef417ecf84ed325
      • eu-west-2: Create entries, one for each of the following:
        • com.amazonaws.vpce.eu-west-2.vpce-svc-0375428488d22c05b
        • com.amazonaws.vpce.eu-west-2.vpce-svc-0c6fedbe99fced2cd
      • us-west-2: Create entries, one for each of the following:
        • com.amazonaws.vpce.us-west-2.vpce-svc-045eebdf710e1066d
        • com.amazonaws.vpce.us-west-2.vpce-svc-060e0d5f582365b8e
        • com.amazonaws.vpce.us-west-2.vpce-svc-07b750990c172f22f
        • com.amazonaws.vpce.us-west-2.vpce-svc-0a7b662960507808f
        • com.amazonaws.vpce.us-west-2.vpce-svc-0ed672a4d41b5e687
      • ap-southeast-1: Create entries, one for each of the following:
        • com.amazonaws.vpce.ap-southeast-1.vpce-svc-00eb29496a51d8bee
        • com.amazonaws.vpce.ap-southeast-1.vpce-svc-01c64edf7fe936ac7
        • com.amazonaws.vpce.ap-southeast-1.vpce-svc-028cc7060eb23ff43
        • com.amazonaws.vpce.ap-southeast-1.vpce-svc-07c68d307f9f05687
      • ap-southeast-2:
        • com.amazonaws.vpce.ap-southeast-2.vpce-svc-031161490f5647f32
      • sa-east-1: Create entries, one for each of the following:
        • com.amazonaws.vpce.sa-east-1.vpce-svc-03cf6c871b7ae95e8
        • com.amazonaws.vpce.sa-east-1.vpce-svc-061204a851dbd1a47
    5. Click Verify service. If successful, you should see a Service name verified message.

      VPC Create endpoint

      If not successful, ensure that your service name matches the region where you're creating the VPC endpoint.

    6. Select the VPC where your application is deployed.

    7. Add the availability zones and associated subnets you want to support.

    8. Click Create endpoint to complete the setup of the endpoint service.

      VPC Create endpoint

    9. Note your VPC Endpoint ID. You will need it in the next step.

      VPC Create endpoint

  2. Add your VPC endpoint ID to your Neon organization

    Assign your VPC Endpoint ID to your Neon organization. If the region has multiple Service Names, please assign all VPC Endpoint IDs. You can do this using the Neon CLI or API.

    note

    Please note that you must assign the VPC Endpoint ID, not the VPC ID.

    In the following example, the VPC endpoint ID is assigned to a Neon organization in the specified AWS region using the neon vpc endpoint command.

    neon vpc endpoint assign vpce-1234567890abcdef0 --org-id org-bold-bonus-12345678 --region-id aws-us-east-2

    You can find your Neon organization ID in your Neon organization settings, or you can run this Neon CLI command: neon orgs list

    Optionally, you can limit access to a Neon project by allowing connections only from a specific VPC endpoint. For instructions, see Assigning a VPC endpoint restrictions.

  3. Enable private DNS

    After adding your VPC endpoint ID to your Neon organization, enable private DNS lookup for the VPC endpoint in AWS.

    1. In AWS, select the VPC endpoint you created.
    2. Choose Modify private DNS name.
    3. Select Enable for this endpoint.
    4. Save your changes. Enable private DNS
  4. Check your database connection string

    Your connection string doesn't change when you use Private Networking.

    To verify that your connection is working correctly, you can perform a DNS lookup on your Neon endpoint hostname from within your AWS VPC. It should resolve to the private IP address of the VPC endpoint.

    For example, if your database connection string is:

    postgresql://alex:AbC123dEf@ep-cool-darkness-123456.us-east-2.aws.neon.tech/dbname?sslmode=require&channel_binding=require

    You can run the following command from an EC2 instance inside your AWS VPC:

    nslookup ep-cool-darkness-123456.us-east-2.aws.neon.tech
  5. Restrict public internet access

    At this point, it's still possible to connect to a database in your Neon project over the public internet using a database connection string.

    You can restrict public internet access to your Neon project via the Neon CLI or API.

    Blocking public access doesn't protect every Neon service

    This step restricts Postgres connections only. It doesn't protect the Data API, Realtime, Managed Better Auth, Object Storage, the AI Gateway, or function URLs. Realtime, Managed Better Auth, and database connections from Neon Functions also stop working. See Private Networking and other Neon services.

    To block access via the Neon CLI, use the neon projects update command with the --block-public-connections option.

    neon projects update orange-credit-12345678 --block-public-connections true

    In the example above, orange-credit-12345678 is the Neon project ID. You can find your Neon project ID under your project's settings in the Neon Console, or by running this Neon CLI command: neon projects list

Assigning a VPC endpoint restriction

You can limit access to a Neon project by allowing connections only from specified VPC endpoints. Use the Neon CLI or API to set a restriction.

You can specify a CLI command similar to the following to restrict project access:

neon vpc project restrict vpce-1234567890abcdef0 --project-id orange-credit-12345678

You will need to provide the VPC endpoint ID and your Neon project ID. If the region has multiple Service Names, all VPC Endpoint IDs must be restricted in the way as above. You can find your Neon project ID under your project's settings in the Neon Console, or by running this Neon CLI command: neon projects list

After adding a restriction, you can check the status of the VPC endpoint to view the restricted project using the vpc endpoint status command. You will need to provide your VPC endpoint ID, region ID, and Neon organization ID.

neon vpc endpoint status vpce-1234567890abcdef0 --region-id=aws-eu-central-1 --org-id=org-nameless-block-72040075
VPC Endpoint ID              vpce-1234567890abcdef0
State                        new
Num Restricted Projects      1
Example Restricted Projects  orange-credit-12345678

Manage private networking with the Neon CLI

You can use the Neon CLI vpc command to manage Private Networking configurations in Neon.

The vpc command includes endpoint and project subcommands for managing VPC endpoints and project-level VPC endpoint restrictions:

  • vpc endpoint: List, assign, remove, and check the status of VPC endpoints for a Neon organization.
  • vpc project: List, configure, or remove VPC endpoint restrictions for specific Neon projects.

The neon vpc endpoint list command requires the --region-id option.

For more details and examples, see Neon CLI commands for vpc.

Manage private networking with the Neon API

The Neon API provides endpoints for managing VPC endpoints and project-level VPC endpoint restrictions:

APIs for managing VPC endpoints

APIs for managing VPC endpoint restrictions

Private Networking and other Neon services

When you restrict public internet access, only connections that arrive through your VPC endpoint can reach Postgres. This restriction covers Postgres connections only. Before you block public access, check which Neon services your project uses. Blocking public access doesn't protect any other Neon service, so don't rely on it for their security. Some of them also stop working once public access is blocked.

ServiceWith public internet access blocked
Postgres connections, including the serverless driverAllowed only through your VPC endpoint
Data APINot protected. Requests from the public internet are still served. The Data API isn't supported with Private Networking.
RealtimeNot protected, and stops working. Subscriptions fail to connect.
Managed Better AuthNot protected, and stops working. Sign-in and other auth requests fail.
Neon FunctionsNot protected, and database connections fail. Function URLs are still reachable, but a function can't connect to Postgres through DATABASE_URL.
Object Storage and the AI GatewayNot protected. Access is controlled by credentials only.

If you haven't blocked public internet access, these services connect over the public internet as usual.

Private networking limits

The Private Networking feature supports a maximum of 20 private networking configurations per AWS region. Supported AWS regions are listed above. If you need more, you can request a limit increase. Scale plan users can request a limit increase from the console.

Limitations

If you remove a VPC endpoint from a Neon organization, that VPC endpoint cannot be added back to the same Neon organization. Attempting to do so will result in an error. In this case, you must set up a new VPC endpoint.

Need help?

Join our Discord Server to ask questions or see what others are doing with Neon. For paid plan support options, see Support.

Last updated on

Was this page helpful?
Edit on GitHub