This page explains what Memorystore for Redis instances are. It also explains important settings and attributes of Redis instances. To learn how to create Redis instances, see Creating and Managing Redis Instances.

What is a Memorystore for Redis instance?

In Memorystore for Redis, an instance refers to an in-memory Redis data store. Memorystore for Redis Instances are also referred to as Redis instances. When you create a new Memorystore for Redis instance, you are creating a new Redis data store.

Instance IDs

Instances are identified by an Instance ID. You choose the Instance ID when you create an instance.

Service Tiers

Memorystore for Redis offers two service tiers: Basic and Standard. The Basic Tier is best suited for applications that use Redis as a cache because data persistence isn't guaranteed during scaling or instance failures. The Standard Tier provides a highly available Redis instance with automatic failover and minimal data loss.

Also, Basic Tier instances and Standard Tier instances behave differently during scaling. Basic Tier instances experience downtime and a full cache flush when scaling up or down. Standard Tier instances are highly available, even during scaling, due to automatic failover.

Capacity tiers

When you create an instance, you select a size between 1-300 GB. The instance's size puts it in one of five capacity tiers, which determine the maximum network performance and price of your instance.

When creating your Redis instance, determine the storage needs of your application and the network throughput you want, and size your instance accordingly.


Redis instances can only connect using VPC networks. Redis instances cannot connect using legacy networks.

Regions and zones

An instance's region and zone have pricing, performance, and networking implications for your application. Google Cloud resources (such as Compute Engine VM instances) need to be in the same region as your Redis instance to access it. Also, keeping resources located in nearby locations improves performance. Redis instances are available in these regions:

  • Belgium (europe-west1)
  • Delhi (asia-south2)
  • Finland (europe-north1)
  • Frankfurt (europe-west3)
  • Hong Kong (asia-east2)
  • Iowa (us-central1)
  • Jakarta (asia-southeast2)
  • Las Vegas (us-west4)
  • London (europe-west2)
  • Los Angeles (us-west2)
  • Melbourne (australia-southeast2)
  • Montréal (northamerica-northeast1)
  • Mumbai (asia-south1)
  • Netherlands (europe-west4)
  • Northern Virginia (us-east4)
  • Oregon (us-west1)
  • Osaka (asia-northeast2)
  • Salt Lake City (us-west3)
  • São Paulo (southamerica-east1)
  • Seoul (asia-northeast3)
  • Singapore (asia-southeast1)
  • South Carolina (us-east1)
  • Sydney (australia-southeast1)
  • Taiwan (asia-east1)
  • Tokyo (asia-northeast1)
  • Toronto (northamerica-northeast2)
  • Warsaw (europe-central2)
  • Zurich (europe-west6)

What's next