Use VPC Service Controls with Memorystore for Valkey

You can protect your Memorystore for Valkey instances using VPC Service Controls.

VPC Service Controls protect against data exfiltration and provide an extralayer of security for your instances. For more information aboutVPC Service Controls, seeOverview 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 perimetermust have the proper access level rules.

Note: Modifications to VPC Service Controls settings forMemorystore for Valkey take on the order of minutes to take effect.

Protect your Valkey instances using VPC Service Controls

  1. Create a service perimeter.

  2. Add the Memorystore for Valkey API to your service perimeter. Forinstructions on adding a service to your service perimeter, seeUpdating a service perimeter.

Configuration requirements

If you use both Shared VPC and VPC Service Controls, you must havethe host project that provides the network and the service project that containsthe Valkey instance inside the same perimeter in order for Valkey requests tosucceed. Otherwise, requests between the service project instance and the hostproject network are blocked by the VPC Service Controls service perimeter.

At any time, separating the host project and service project with a perimetercan cause a Valkey instance failure, in addition to blocked requests.

For more information about limitations when using VPC Service Controls withMemorystore for Valkey, seeMemorystore for Valkey.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.