Use VPC Service Controls with Memorystore for Redis
Stay organized with collections
Save and categorize content based on your preferences.
You can protect your Memorystore for Redis instances using VPC Service Controls.
VPC Service Controls protect against data exfiltration and provide an extra
layer of security for your instances. For more information about
VPC Service Controls, see Overview of VPC Service Controls.
Once the Memorystore for Redis API is protected by your service perimeter,
Memorystore for Redis API requests coming from clients outside of the perimeter
must have the proper access level rules.
Protecting your Redis instances using VPC Service Controls
Add the Memorystore for Redis API to your service perimeter. For
instructions on adding a service to your service perimeter, see
Updating a service perimeter.
Configuration requirements
If you use both Shared VPC and VPC Service Controls, you must have the host
project that provides the network and the service project that contains the
Redis instance inside the same perimeter in order for Redis requests to succeed.
Otherwise, requests between the service project instance and the host project
network are blocked by the VPC Service Controls service perimeter.
At any time, separating the host project and service project with a perimeter
can cause a Redis instance failure, in addition to blocked requests.
Limitations of VPC Service Controls for Redis instances
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Use VPC Service Controls with Memorystore for Redis\n\nYou can protect your Memorystore for Redis instances using VPC Service Controls.\n\nVPC Service Controls protect against data exfiltration and provide an extra\nlayer of security for your instances. For more information about\nVPC Service Controls, see [Overview of VPC Service Controls](/vpc-service-controls/docs/overview).\n\nOnce the Memorystore for Redis API is protected by your service perimeter,\nMemorystore for Redis API requests coming from clients outside of the perimeter\nmust have the proper access level rules.\n\nProtecting your Redis instances using VPC Service Controls\n----------------------------------------------------------\n\n1. [Create a service perimeter](/vpc-service-controls/docs/create-service-perimeters).\n\n2. Add the Memorystore for Redis API to your service perimeter. For\n instructions on adding a service to your service perimeter, see\n [Updating a service perimeter](/vpc-service-controls/docs/manage-service-perimeters#update).\n\nConfiguration requirements\n--------------------------\n\nIf you use both Shared VPC and VPC Service Controls, you must have the host\nproject that provides the network and the service project that contains the\nRedis instance inside the same perimeter in order for Redis requests to succeed.\nOtherwise, requests between the service project instance and the host project\nnetwork are blocked by the VPC Service Controls service perimeter.\n\nAt any time, separating the host project and service project with a perimeter\ncan cause a Redis instance failure, in addition to blocked requests.\n\nLimitations of VPC Service Controls for Redis instances\n-------------------------------------------------------\n\nFor a list of VPC Service Controls limitations for\nMemorystore, see [Supported products and limitations](/vpc-service-controls/docs/supported-products#memstore-redis)"]]
