Last updated June 02, 2026

This article describes how to use AWS PrivateLink to create a secure connection between an Amazon Virtual Private Cloud (AWS VPC) and a Heroku Postgres database running in a Private Space or a Shield Private Space. This process involves three high-level steps:

1. Creating an endpoint service on your Private or Shield Heroku Postgres database
2. Creating an endpoint network interface in your AWS VPC
3. Establishing the secure connection between the two endpoints

As part of setting up the connection, you can specify a list of approved accounts to limit access to your Heroku Postgres database from the VPC.

Heroku Prerequisites

The following Heroku resources are required to set up a PrivateLink endpoint:

• A Private Space or Shield Private Space. Create a Private Space or a Shield Private Space using either the Heroku Dashboard or the Heroku CLI.
• A Heroku app running in the Private Space or Shield Private Space with an attached Heroku Postgres database. All Heroku Postgres instances running in a Private Space or a Shield Private Space use one of the private or shield plan types, respectively. See Provisioning Heroku Postgres on how to create a database.

Provisioning the Heroku Endpoint

Step 1: Install the Heroku Data via PrivateLink CLI Plugin

To install the CLI plugin, run the command:

$ heroku plugins:install @heroku-cli/plugin-data-privatelink

Step 2: Obtain Your AWS Account ID

You can obtain your AWS account ID with the AWS CLI:

$ aws sts get-caller-identity --output text --query 'Account'

123456789101

The example command returns an account ID of 123456789101.

You can also obtain your account ID from the Account page of your AWS account. The Account ID is the Account Details section:

Step 3: Create a PrivateLink Endpoint

Create a PrivateLink endpoint using the following Heroku CLI command and substitute the values:

$ heroku data:privatelink:create POSTGRESQL_ADDON_NAME --aws-account-id ACCOUNT_ID --app APP_NAME

• Replace POSTGRESQL_ADDON_NAME with the name of your Heroku Postgres database, for example, postgresql-simply-12345.
• Replace APP_NAME with your app’s name.
• Replace ACCOUNT_ID with the AWS account that receives access to your Heroku Postgres database. This ID can match any of the following patterns:
  • account-id
  • account-id:user/username
  • account-id:role/rolename

Here’s an example command with the output:

$ heroku data:privatelink:create postgresql-simply-12345 --aws-account-id 123456789101:user/abc.xyz -a example-app
Creating privatelink endpoint... done

Service Name: Provisioning
Status:       Provisioning

The privatelink is now being provisioned for postgresql-simply-12345.
Run heroku data:privatelink:wait postgresql-simply-12345 –app example-app to check the creation process.

Step 4: Obtain Your Endpoint’s Service Name

When the PrivateLink endpoint finishes provisioning, use the command to view its details:

$ heroku data:privatelink POSTGRESQL_ADDON_NAME --app APP_NAME

Replace POSTGRESQL_ADDON_NAME with the name of your Heroku Postgres database, and replace APP_NAME with your app’s name.

Here’s an example command with the output:

$ heroku data:privatelink postgresql-simply-12345 --app example-app
=== privatelinks for postgresql-simply-12345
Service Name:         com.amazonaws.vpce.us-east-1.vpce-svc-0410a2e25933fe8ec
Status:               Operational

=== Allowed Accounts
ARN                                    Status
arn:aws:iam::123456789101:user/abc.xyz Active

Your privatelink endpoint is now operational.
You must now copy the Service Name and follow the rest of the steps listed in https://devcenter.heroku.com/articles/heroku-postgres-via-privatelink.

Copy the value of the Service Name field from the command’s output. In the previous example, the service name is com.amazonaws.vpce.us-east-1.vpce-svc-0410a2e25933fe8ec. You need this value to provision the Amazon VPC endpoint.

Provisioning the Amazon VPC Endpoint

You perform the steps in this section from your Amazon VPC dashboard.

Step 1: Create and Configure a Security Group

Your endpoint requires a security group with appropriate ingress security rules. To create a security group:

1. Click Create security group in the Security Groups tab of your VPC dashboard.
2. In the Basic details section, specify a security group name and description, and select your target VPC.
3. In the Inbound rules section, click to Add rule.
4. Enable Custom TCP access to ports 5432–5433 from any valid IP address.
5. Click Create security group.

Step 2: Create the Endpoint

To create an endpoint:

1. Navigate to the Endpoints tab of your VPC dashboard and click Create Endpoint.

2. Give a name for your endpoint in the Name tag field.

3. In the Type section, select the PrivateLink Ready partner services category.

4. In the Service settings section, paste the Service name value you obtained earlier.

5. Click Verify service to show the list of available subnets.

   

6. In the Network Settings section, select the VPC you specified when creating the Security Group.

7. In the Subnets section, select the subnets to enable and the Subnet ID, and select the IP address type to use.

8. In the Security group section, select the security group you created in the previous step, and click Create endpoint.

   

You see the endpoint you created with an initial status of pending acceptance, which transitions to available after 5-10 minutes.

You can also confirm it’s available from the Heroku Dashboard. Navigate to the Settings tab in your database and click Show Configuration under the Heroku Postgres via PrivateLink section. You can see the connection status under Connections.

Connecting the Heroku and Amazon VPC Endpoints

After the Amazon VPC endpoint becomes available, you can obtain the URLs from the config var that Heroku creates to allow your VPC to communicate with your Heroku Postgres database (DATABASE_ENDPOINT_ID_URL) and PgBouncer (DATABASE_ENDPOINT_ID_PGBOUNCER_URL).

The config var name with the endpoint’s connection string includes the last 17 characters of your endpoint ID, in uppercase. For example, if the endpoint ID is vpce-01c87ae3c05563935, the config var name uses 01C87AE3C05563935.

List your app’s config vars and search the config var for your endpoint, replacing ENDPOINT_ID:

$ heroku config --app example-app | grep -i ENDPOINT_ID

This command displays the AWS VPC endpoint connection URL and the corresponding connection string for your Heroku Postgres database. The connection string has the following format:

postgres://user:password@vpc-endpoint-dns-name:5432/database

You can now use this connection string to connect the apps in your AWS VPC to your private Heroku Postgres database and PgBouncer instance. Here’s an example command with the output:

$ heroku config --app example-app | grep -i 01C87AE3C05563935

DATABASE_ENDPOINT_01C87AE3C05563935_URL:           postgres://abcdefghijklmn:abcdefghijklmnopqrstuvwxyz123456789101112131415161718192021222324@ec2-3-83-63-168.compute-1.amazonaws.com:5432/dd0k757ojc5qt
DATABASE_ENDPOINT_01C87AE3C05563935_PGBOUNCER_URL: postgres://abcdefghijklmn:abcdefghijklmnopqrstuvwxyz123456789101112131415161718192021222324@ec2-3-83-63-168.compute-1.amazonaws.com:5433/dd0k757ojc5qt

You can also get the endpoint connection string from the Heroku Dashboard:

1. Navigate to your database in the Heroku Dashboard and click the Settings tab.
2. Click Show Configuration next to Heroku Postgres via PrivateLink section.
3. Click Reveal Credentials to show the connection string.

Limitations

• You must provision the Amazon VPC endpoint you create in a subnet that’s in the same region as your Heroku Postgres database.
• It’s your responsibility to verify the security of your VPC to ensure fully secure access to your Heroku Postgres database.

Comparison to Private Space Trusted IP Ranges

Private Spaces support trusted IP ranges for data services as a beta feature. This feature is an option if you must connect to a Heroku Postgres database from outside the Private Space boundary. You must contact Heroku to enable this feature, and granular access control isn’t available for it.

By connecting via AWS PrivateLink, it treats your database as part of your own VPC, and you can restrict access to a set of users and roles. We recommend this method when it’s available for your use case.