Amazon MemoryDB for Redis is a Redis-compatible, durable, in-memory database that delivers ultra-fast performance and Multi-AZ durability. With Amazon MemoryDB for Redis, you only pay for what you use with no minimum fee. A node is the smallest building block of a MemoryDB cluster. Each node supports varying amounts of computation and memory capacity, and you can select a node type based on your needs. You are charged based on three components: on-demand instance hours per node, volume of data written to your cluster, and snapshot storage that you use.
Get started with Amazon MemoryDB for Redis for free
As part of the AWS Free Tier, you can get started with MemoryDB for free. Upon signup, new MemoryDB customers receive 750 hours of MemoryDB on db.t4g.small instances and 20 GB of data per month free for 2 months.
The Amazon AWS Free Tier applies to participating services across our global regions. Your free usage under the AWS Free Tier is calculated each month across all regions and automatically applied to your bill – free usage does not accumulate. The AWS Free Tier is not available in the AWS GovCloud (US) regions or the China (Beijing) region at this time.
On-Demand instance hours per node: On-demand instance hours per node is the amount of node capacity for a cluster, charged per instance-hour consumed.
Data Written: Data written is the volume of data written to a cluster, charged per GB.
Snapshot Storage: Snapshot storage is the storage associated with the automated and user-initiated snapshots you take, charged per GB-month.
On-demand nodes let you pay by the instance hour with no long-term commitments or upfront fees. This frees you from the costs and complexities of planning, purchasing, and maintaining hardware, and transforms what are commonly large fixed costs into much smaller variable costs. The node type impacts the compute, in-memory data storage capacity, and network throughput available for your MemoryDB cluster.
Nodes with data tiering use solid state drives (SSD) to automatically optimize costs of your MemoryDB clusters by moving the least frequently used items from memory to SSD. Data stored on SSD exhibits slightly higher latency and lower throughput compared to data stored in memory. Nodes with data tiering, available for MemoryDB for Redis, are ideal for workloads that access up to 20% of their data regularly, and for applications that can tolerate additional latency the first time a less-frequently accessed item is needed. Amazon MemoryDB R6gd nodes with memory and solid state drives have nearly 5x more total storage capacity and can help customers achieve over 60% storage cost savings when running at maximum utilization compared to MemoryDB R6g nodes with memory only. See Pricing Example 3 below for a comparison on how data tiering can reduce your spend.
You pay only for the volume of data (in GB) you write to your MemoryDB cluster. This data includes the Redis key, value, and command volume. There are no associated costs for reads.
Snapshot storage for a MemoryDB cluster is the storage associated with the automated and user-initiated snapshots you take. A snapshot is a copy of an entire cluster at the time when the snapshot was taken. There is no additional charge for snapshot storage of up to 100% of your total MemoryDB cluster storage for a region. There is no additional charge for snapshot storage if your snapshot retention period is 1 day. Additional snapshot storage is billed at storage rates in the table below:
Pricing Example 1
You are building an application that requires a database that provides fast data access to enable a responsive, real-time user experience for a regional logistics company. The application has a total dataset size of 25 GB. On average, 3% of the data is updated every hour. You use a MemoryDB architecture with one shard that includes one primary and one replica node per shard to meet the application requirements. You choose the db.r6g.xlarge node type as it has enough memory to fit the entire working dataset. You also choose to deploy your workload in U.S. West (Oregon). Additionally, you set your snapshot retention to 2 days enabling you to store the snapshot free of charge for the first day and charging you for snapshot storage for the additional day.
Pricing Example 2
You work at a media and entertainment company and your team built an application that requires very low latency and high throughput. To meet these performance requirements, you use Amazon MemoryDB for Redis as your primary database. The application is read-heavy and has a total dataset size of 50 GB consisting of 100 byte objects (includes Redis key, value and command size). The application is 80% reads and 20% writes, and approximately 50,000 transactions per second. You choose two shards of db.r6g.xlarge node type to have enough memory to fit the entire dataset in the cluster (50GB) and select one replica per shard to support the reads of the application and high availability. You also choose to deploy your workload across two availability zones (AZs) in U.S. East (N. Virginia) for high availability. Additionally, you set your snapshot retention to 2 days allowing you to store the snapshot free of charge for the first day and charging you for snapshot storage for the additional day. Your total charges are calculated as follows: