Announcing the general availability of Amazon MemoryDB Multi-Region
Today, AWS announces the general availability of Amazon MemoryDB Multi-Region, a fully managed, active-active, multi-Region database that lets you build multi-Region applications with up to 99.999% availability and microsecond read and single-digit millisecond write latencies. MemoryDB is a fully managed, Valkey- and Redis OSS-compatible database service providing multi-AZ durability, microsecond read and single-digit millisecond write latency, and high throughput. Valkey is an open source, high performance, key-value data store—stewarded by Linux Foundation—and is a drop-in replacement of Redis OSS.
With MemoryDB Multi-Region, you can build highly available multi-Region applications for increased resiliency. It offers active-active replication so you can serve reads and writes locally from the Regions closest to your customers with microsecond read and single-digit millisecond write latency. MemoryDB Multi-Region asynchronously replicates data between Regions and typically propagates data within a second. It automatically resolves update conflicts and corrects data divergence issues, so you can focus on building your application.
Get started with MemoryDB Multi-Region from the AWS Management Console or using the latest AWS SDK or AWS Command Line Interface (AWS CLI). First, you need to identify the set of AWS Regions where you want to replicate your data. Then choose an AWS Region to create a new multi-Region cluster and a regional cluster. Once the first regional cluster is created, you can add up to four additional Regions to the multi-Region cluster.
MemoryDB Multi-Region is available for Valkey in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (London). To learn more, please visit the MemoryDB features page, getting started blog, and documentation. For pricing, please refer to the MemoryDB pricing page.