Skip to content

Set up AWS PrivateLink with PlanetScale Managed

Managed

Learn how to set up AWS PrivateLink to establish private database connectivity with PlanetScale Managed.

Overview

PlanetScale Managed can connect you to your databases via AWS PrivateLink. The following guide describes how PlanetScale Managed with AWS PrivateLink works and how to set it up.

Note

AWS PrivateLink is only available on single-tenancy PlanetScale deployment options, including PlanetScale Managed. It is not available on Scaler Pro plans or other multi-tenancy deployments. If you are interested in PlanetScale Managed, please contact us.

AWS PrivateLink requires two components:

  • A VPC endpoint service deployed in the sub-account that PlanetScale controls.
  • A VPC endpoint interface, sometimes referred to as a "VPC endpoint" in AWS, deployed in the account that your applications operate in.

Once both components are operating correctly, the EC2 instances in the VPC that the VPC endpoint has been assigned to will leverage Private DNS to connect to your VPC endpoint instead of the publicly accessible endpoint.

The connection strings that PlanetScale provides will operate successfully inside and outside your VPC, creating PrivateLink connections inside of your VPC and regular connections outside of your VPC.

Step 1: Initiating the setup process

There is no fully automated way to establish a PrivateLink connection. If you would like to initiate the process, please get in touch with your Solutions Engineer and let them know the AWS Account ID that you intend to create the VPC endpoint in.

Once they receive your AWS Account ID and forward it to the team responsible for provisioning your deployment, the team will provide the Solutions Engineer (and ultimately you) with the Service Name of the VPC endpoint service that will be responsible for accepting your connection.

Note

It is important to keep the service name in your records. It is the only piece of information you need to input when creating your VPC endpoint.

Step 2: Establishing a VPC endpoint connection

Warning

Only proceed to the next steps once a PlanetScale Solutions Engineer has provided the service name and confirmed cross-account authentication has been configured.

The following steps are an example of establishing a VPC endpoint connection in the AWS Console. In this example, the customer has requested that their deployment be in the eu-west-1 region.

When you go through the steps, make sure that you have selected the region that matches the region that your PlanetScale Managed cluster deployment has been provisioned into.

  1. Navigate to the Endpoints section on the Virtual Private Cloud page and select "Create Endpoint."

  1. Select the "Find service by name" selector, input the provided Service Name, and select the "Verify" button.

  1. Select the VPC in the drop-down where you wish to provision this VPC endpoint and the relevant subnets inside your VPC.

  1. Select the "Enable DNS Name" checkbox. Take note of the value of your "Private DNS Name" field. That is how we will verify that the connection is operating successfully.

  1. Select the relevant Security Groups you want your VPC endpoint to adhere to.

  1. Add as many tags as your heart desires (up to 50) and select "Create endpoint."

  1. The "Creating" spinner will spin momentarily and then deliver you the news of the endpoint creation. You should see a VPC endpoint in the pending state if it was successful. If the creation failed, record the reason and consult your Solutions Engineer.

  1. After 2-10 minutes (make sure to refresh), your VPC endpoint will report an available state.

Step 3: Verifying a VPC endpoint connection

PlanetScale publishes a wildcard DNS record for your private region. AWS PrivateLink will override the DNS record in your VPC to point to your VPC endpoint instead of the publicly published record.

To verify that the DNS override is working correctly, issue the following dig command using the value of your "Private DNS Name" instead of the value in the example:

Terminal
dig +short wildcard.frzzbztuqm3h-euwest1-1.psdb.cloud

172.31.16.197

172.31.13.7

If your dig command returns a set of static IP addresses, your VPC Endpoint connection is operating successfully. If it returns a CNAME to an ELB record (for example, something like something.elb.region.amazoneaws.com), your connection is not operating successfully, and you should consult your Solutions Engineer.

Once you've verified that your connection is operating successfully, you will need to verify that you can reach a database you've provisioned:

  1. Create a connection string for a PlanetScale database using the "Connect" button. Select "MySQL CLI" and copy the command.
  2. Paste your MySQL CLI command into a command prompt of an EC2 instance running in your VPC with the mysql-client package installed:
Terminal
mysql -h <HOST_NAME> -u <USERNAME> -p --ssl-mode=VERIFY_IDENTITY --ssl-ca=/etc/pki/tls/certs/ca-bundle.crt

Enter password:

...




mysql>

Note: The correct path for the CA root configuration for the --ssl-ca flag depends on your operating system. See the CA root configuration documentation for more the correct path.

If you receive the mysql> prompt, your connection is operating successfully, and you have just confirmed that your connections to PlanetScale will be established through AWS PrivateLink. If you do not receive the mysql> prompt, please consult your Solutions Engineer.

Need help?

Get help from the PlanetScale support team, or join our GitHub discussion board to see how others are using PlanetScale.

Was this page useful?
Last updated on Help us improve this page