Last updated November 22, 2022

This article describes how to use AWS PrivateLink to create a secure connection between an AWS VPC and a Heroku Data for Redis add-on 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 Data for Redis add-on
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 private addon 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 Data for Redis add-on. All Heroku Data for Redis instances running in a Private Space use one of the private plan types. All Heroku Shield for Redis instances running in a Shield Private Space use one of the shield plan types.

Provisioning the Heroku Endpoint

Step 1: Install the Heroku Data via PrivateLink CLI plugin

$ heroku plugins:install 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 above returns an account ID of 123456789101.

You can also obtain your account ID from the My Account page of your AWS account. The Account ID is shown in the Account Settings section:

Step 3: Create a PrivateLink Endpoint

Create a PrivateLink endpoint using the following Heroku CLI command (note the values to substitute below):

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

• Replace REDIS_ADDON_NAME with the name of your Redis addon (for example, redis-sushi-12345).
• Replace APP_NAME with your app’s name.
• Replace ACCOUNT_ID with the AWS account that should receive access to your Redis addon. 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 accompanying output:

$ heroku data:privatelink:create redis-sushi-12345 --aws-account-id 123456789101:user/abc.xyz --app privatelink-vpc-endpoint-demo
Creating privatelink... done

Service Name: Provisioning
Status:       Provisioning

The PrivateLink is now being provisioned for redis-sushi-12345.
Run heroku data:privatelink:wait REDIS_URL -a APP to check the creation process.

Step 4: Obtain Your Endpoint’s Service Name

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

$ heroku data:privatelink REDIS_ADDON_NAME --app APP_NAME

Replace REDIS_ADDON_NAME with the name of your private Redis addon, and replace APP_NAME with your app’s name.

Here’s an example command with accompanying output:

$ heroku data:privatelink redis-sushi-12345 --app privatelink-vpc-endpoint-demo
=== privatelinks for redis-sushi-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 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-redis-via-privatelink.

Copy the value of the Service Name field from the command’s output (in the example above, the value 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. Click Create security group in the Security Groups tab of your VPC dashboard:

Specify an appropriate security group name and description and select your desired VPC before clicking Create:

Select your newly created security group from the list and click Actions > Edit inbound rules:

Enable TCP access to ports 6379 from any valid IP address and click Save rules.

Step 2: Create the Endpoint

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

In the Create Endpoint form that appears, select the Find service by name option and paste the Service Name value you obtained earlier.

Then click Verify to display the list of available subnets:

Attach the security group you created earlier to the VPC Endpoint and click Create endpoint:

The endpoint is created with an initial status of pending acceptance, which transitions to available after 5-10 minutes:

Connecting the Heroku and Amazon VPC Endpoints

After the Amazon VPC endpoint becomes available, you can obtain the URL that allows your VPC to communicate with your Heroku Data for Redis addon.

First, obtain your PrivateLink endpoint’s Endpoint ID and extract the 17-character string that appears at the end of it. Convert that string to upper case and use it in the command below.

For example, if the Endpoint ID is vpce-01c87ae3c05563935, the Endpoint ID is 01C87AE3C05563935.

Run the following command, substituting the obtained string where indicated:

$ heroku config --app your_app_name | grep ENDPOINT_ID_HERE

This command displays the AWS VPC Endpoint connection URL and the corresponding connection string for your Redis Addon. The connection string has the following format:

redis://user:password@vpc-endpoint-dns-name:6379

You can now use this connection string to connect the applications in your AWS VPC to your private Heroku Data for Redis addon. Here’s an example command with accompanying output:

$ heroku config --app privatelink-vpc-endpoint-demo | grep 01C87AE3C05563935

REDIS_ENDPOINT_01C87AE3C05563935_URL:           redis://user:password@vpc-endpoint-dns-name:6379

Connecting to Heroku Data for Redis from EC2 via VPC Endpoints

After you configure your VPC endpoints, you can create an EC2 instance in your AWS VPC to connect to Heroku Data for Redis.

Click Launch Instance in your EC2 dashboard and select your AMI and Instance Type. In this example, an Ubuntu t2.micro instance is created:

When configuring the instance’s details, select the VPC network with the security group you created earlier and pick an appropriate subnet. Click Review and Launch and launch the EC2 instance.

After the instance’s status transitions to running and all status checks have passed, connect to the instance using the SSH key pair you specified during instance creation.

After connecting to the instance, use the connection string to connect to Redis securely but note that the port number will be 6379 not 6380 as it is when connecting via stunnel.

The following output shows the connection string being used to connect to a Heroku Data for Redis addon from within a sample EC2 instance with Ruby:

ᐅ ssh ubuntu@ec2-1-2-3-4.compute-1.amazonaws.com
Welcome to Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-1021-aws x86_64)
...<snip>...
ubuntu@ip:~$ sudo apt install ruby && sudo gem install redis
...<snip>...
ubuntu@ip:~$ irb
irb(main)> require "redis"
=> true
irb(main)> url = URI.parse("redis://password@vpce-id-secret.vpce-svc-id.us-east-1.vpce.amazonaws.com:6379")
irb(main)> url.scheme = "rediss"
irb(main)> $redis = Redis.new(url: url, driver: :ruby, ssl_params: { verify_mode: OpenSSL::SSL::VERIFY_NONE })
irb(main)> $redis.ping
=> "PONG"

Limitations

• The Amazon VPC Endpoint you create must be provisioned in a subnet that is in the same region as your Heroku Data for Redis addon.
• You can only connect to your private Redis addon in Availability Zones that are common between your own VPC and the Heroku Data VPC.
• It is your responsibility to verify the security of your VPC to ensure fully secure access to your Heroku Data for Redis addon.