VPC peering in Redis Cloud Pro allows secure, high-performance private connectivity between your application VPC and Redis Cloud infrastructure. This guide walks through setting up peering connections for both AWS and Google Cloud, updating route tables, switching to private endpoints, and resolving common configuration issues. By the end, you’ll have a fully private connection path between your app and Redis Cloud, optimized for security and low latency.
Prerequisites
VPC peering is only available on Redis Cloud Pro subscriptions. It isn't supported in Essentials plans.
Your application VPC’s CIDR must not overlap with Redis Cloud’s VPC CIDR.
A single Pro subscription can support multiple peerings if each VPC CIDR range is unique.
For a technical overview of Redis Cloud's VPC peering implementation, see the Redis Docs: Enable VPC Peering.
Step-by-Step Instructions
AWS VPC Peering
Initiate Peering in Redis Cloud
Log in to the Redis Cloud Console.
Navigate to Subscriptions > Connectivity > VPC Peering.
-
Click Add peering and enter the following:
Consumer AWS Account
Consumer Region
Consumer VPC ID
Consumer VPC CIDRs (Up to 48 primary & secondary, non-overlapping)
Click Initiate peering and save the Peering ID for later use.
Approve Peering in AWS
-
In the AWS VPC Console, locate and approve the incoming VPC peering request.
For additional details: Accept or reject a VPC peering connection
Click Modify my route tables now (this becomes active after AWS approval)
Update AWS Route Tables
In AWS, go to the VPC route table associated with your application subnet.
-
Add a new route:
Destination: Redis Cloud VPC CIDR (displayed in Redis Cloud and when accepting the peering request in the AWS UI)
Target: Choose the Peering Connection by the saved Peering ID.
For help updating your AWS route table, refer to AWS: Update your route tables for a VPC peering connection
Switch to Private Endpoint
In your database configuration, locate the private endpoint and replace your application’s connection string with this private address.
Update CIDR Allow List (If Applicable)
If your Redis Cloud database uses IP allowlists, you must add your peered VPC CIDRs under Security > IP Access Control to permit traffic over the private network.
Google Cloud VPC Peering
Initiate Peering in Redis Cloud
Go to Subscriptions > Connectivity > VPC Peering, then click Add peering.
-
Provide:
Project ID
Network Name
Redis Cloud generates a
gcloudCLI command. Copy this for the next step.Click Initiate peering and save the Cloud Peering ID.
Approve in Google Cloud
Paste and run the provided command using the Google Cloud SDK.
For more information on permissions or role setup, see Google Cloud VPC Peering Overview.
Switch to Private Endpoint
Use the private endpoint displayed in your Redis Cloud database page to update your app’s connection string.
Update CIDR Allow List (If Applicable)
If your Redis Cloud database enforces IP restrictions, ensure your GCP VPC CIDRs are added to the allowlist.
Troubleshooting & Common Issues
| Issue | Resolution |
|---|---|
| CIDR Overlap | Ensure the VPC CIDRs between your app and Redis Cloud do not overlap. |
| Route Table Misconfiguration | Check that routes are properly set in AWS or GCP to direct traffic through the peering connection. More on Route Table Configuration |
| Unrestricted Public Access | Peering does not disable public access. Restrict access by configuring your CIDR allow list. |
| Still Using Public Endpoint | Update your app to use the Redis Cloud private endpoint once peering is complete. |
| Multiple Peerings | Ensure each peered VPC uses a unique CIDR; overlapping ranges will cause failures. |
Onboarding Progress
Previous: Setting Up Alerts in Redis Cloud
Next: This is the final step
You can return to the Redis Cloud Onboarding Overview at any time to track your progress or revisit earlier steps.
0 comments
Please sign in to leave a comment.