Use VPC Service Controls with Memorystore for Valkey
Stay organized with collections
Save and categorize content based on your preferences.
You can protect your Memorystore for Valkey 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 Valkey API is protected by your service perimeter,
Memorystore for Valkey API requests coming from clients outside of the perimeter
must have the proper access level rules.
Protecting your Valkey instances using VPC Service Controls
Add the Memorystore for Valkey 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 Valkey instance inside the same perimeter in order for Valkey 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 Valkey instance failure, in addition to blocked requests.
For more information about limitations when using VPC Service Controls with
Memorystore for Valkey, see Memorystore for Valkey.
[[["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-09-04 UTC."],[],[],null,["# Use VPC Service Controls with Memorystore for Valkey\n\nYou can protect your Memorystore for Valkey 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 Valkey API is protected by your service perimeter,\nMemorystore for Valkey API requests coming from clients outside of the perimeter\nmust have the proper access level rules.\n| **Note:** Modifications to VPC Service Controls settings for Memorystore for Valkey take on the order of minutes to take effect.\n\nProtecting your Valkey 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 Valkey 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\nthe host project that provides the network and the service project that contains\nthe Valkey instance inside the same perimeter in order for Valkey requests to\nsucceed. Otherwise, requests between the service project instance and the host\nproject network 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 Valkey instance failure, in addition to blocked requests.\n\nFor more information about limitations when using VPC Service Controls with\nMemorystore for Valkey, see [Memorystore for Valkey](/vpc-service-controls/docs/supported-products#table_memorystore_for_valkey)."]]
