Bring Your Own VPC

This section explains how to configure Readyset Cloud to deploy the dataplane (i.e. a Readyset cache instance) in your own VPC. This may be necessary for users who want to prevent any data from leaving your own VPC or Cloud.

Please note that the control plane continues to reside on Readyset's Cloud account. Only the Readyset Cluster Instances are deployed to your VPC.

There are 3 main steps that are required to deploy clusters in an external AWS account & dedicated VPC. The diagram below depicts the three steps and a description is provided subsequent to the diagram:

1. Create a dedicated VPC / role in the customer account

This dedicated VPC will be used to host the Readyset instance in your cloud account. For your convenience we provide an automated script that you can download and execute.

1. Download script

2. Execute script from your account through the cloudshell (opens in a new tab)

3. Confirm role (opens in a new tab) has been set up successfully in organization's roles page (opens in a new tab)

2. Set up VPC peering between the Readyset Cluster Instance's VPC and your upstream database VPC.

The high level steps for establishing peering between the Readyset Cluster Instance's VPC and the VPC hosting your database is provided below. Refer to this link (opens in a new tab) for more details.

1. Initiate and accept a VPC peering request between the VPCs

2. Add the peering routes to each VPC’s route tables

3. Allow ingress to your RDS VPC on 5432 / 3306

4. Allow ingress to your ReadySet cluster VPC on 5433 / 3307

3. Specify "external" VPC during Readyset cluster creation

Select “external” VPC deployment type during cluster creation. If the VPC and role are created successfully, you will be able to select this account & VPC to deploy into.