AWS ElastiCache and Google Cloud Memorystore Valkey Support (2024-2026)
Which cloud providers added managed Valkey, and when. The short version: AWS got there first in 2024, Google followed in 2025, and both now default new clusters to Valkey. Azure is the one big-three holdout.
Do AWS and Google Cloud support Valkey? Short answer
Yes. Amazon ElastiCache for Valkey went GA in October 2024 and is the default engine for new ElastiCache clusters. Google Cloud Memorystore for Valkey went GA on 18 April 2025 (preview August 2024) and is the recommended path for new Memorystore instances. DigitalOcean replaced its Managed Redis with Managed Caching for Valkey on 24 April 2025, and Aiven leads with Aiven for Valkey. Microsoft Azure is the exception: it ships no managed Valkey and steers new workloads to Azure Managed Redis (Redis Enterprise) instead.
Managed Valkey support by provider
Valkey: Linux Foundation BSD fork of Redis 7.2.4, RESP-compatible drop-in. Verified June 2026 against AWS, Google Cloud, DigitalOcean, and Azure docs and announcements.
When each cloud added Valkey: 2024, 2025, 2026
The license fork in March 2024 reshaped managed-service defaults in under two years.
Why AWS and Google backed Valkey but Azure did not
When Redis Inc dropped the BSD license for SSPLv1 and RSALv2 in March 2024, the managed-service business model became legally fraught: SSPLv1 specifically targets providers that offer the software as a service. AWS, Google, and Oracle each run large managed in-memory services, so they co-founded the Linux Foundation Valkey fork to keep a BSD-licensed, RESP-compatible drop-in alive. Within months their managed services defaulted to it.
Microsoft took the opposite path. It licenses Redis Enterprise directly from Redis Inc, so Azure Cache for Redis and Azure Managed Redis (GA 19 May 2025) are insulated from the SSPL/AGPL fork. With a commercial relationship already in place, Microsoft had no reason to back Valkey, and Azure ships no managed Valkey to this day. For Valkey on Azure you self-host on VMs or AKS.
Cloud Valkey support FAQ
Do AWS ElastiCache and Google Cloud Memorystore support Valkey?⌄
Yes, both do, and both default to Valkey for new clusters. Amazon ElastiCache for Valkey went GA in October 2024 and is the default engine for new ElastiCache deployments (Redis OSS and Memcached remain selectable; AWS MemoryDB is also Valkey-based). Google Cloud Memorystore for Valkey went GA on 18 April 2025 (preview August 2024) and is the recommended path for new Memorystore instances. Microsoft Azure is the exception: it ships no managed Valkey.
When did AWS ElastiCache add Valkey support?⌄
Amazon ElastiCache for Valkey became generally available in October 2024, roughly seven months after the Linux Foundation forked Valkey from Redis 7.2.4 in March 2024. AWS made Valkey the default engine for new ElastiCache clusters and priced Valkey nodes about 20 percent below Redis OSS, with ElastiCache Serverless for Valkey about 33 percent cheaper than Redis OSS Serverless.
When did Google Cloud Memorystore add Valkey support?⌄
Memorystore for Valkey entered preview in August 2024 and went generally available on 18 April 2025 with a 99.99 percent availability SLA, cross-region replication, persistence, and Private Service Connect. Memorystore for Valkey is the default and recommended path for new Memorystore instances. As of March 2026 Memorystore runs Valkey 9.0.
Does Microsoft Azure support Valkey?⌄
No. Azure ships no managed Valkey and no managed Memcached. Because Microsoft licenses Redis Enterprise directly from Redis Inc, its first-party services (Azure Cache for Redis and the newer Azure Managed Redis, GA 19 May 2025) are insulated from the SSPL/AGPL fork, so Microsoft had no commercial reason to back Valkey the way AWS, Google, and Oracle did. For managed Valkey on Azure you self-host on VMs or AKS.
Which cloud providers support Valkey in 2024, 2025, and 2026?⌄
In 2024, AWS ElastiCache for Valkey went GA (October) and Google Memorystore for Valkey entered preview (August). In 2025, Memorystore for Valkey went GA (18 April) and DigitalOcean replaced Managed Redis with Managed Caching for Valkey (24 April); Azure Managed Redis went GA (19 May) but ships Redis Enterprise, not Valkey. By 2026, AWS ElastiCache and Google Memorystore both default to Valkey, Aiven leads with Aiven for Valkey, and the latest community release is Valkey 9.1 (19 May 2026).