On-Demand Nodes

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.

China (Ningxia) Region

Instance Type Pricing (Ningxia)
db.r6g.large 2.151
db.r6g.xlarge 4.304
db.r6g.2xlarge 8.607
db.r6g.4xlarge 17.213
db.r6g.8xlarge 34.425
db.r6g.12xlarge 51.638
db.r6g.16xlarge 68.850
db.t4g.small 0.285
db.t4g.medium 0.569

China (Beijing) Region

Instance Type Pricing (Beijing)
db.r6g.large 2.970
db.r6g.xlarge 5.942
db.r6g.2xlarge 11.882
db.r6g.4xlarge 23.763
db.r6g.8xlarge 47.526
db.r6g.12xlarge 71.291
db.r6g.16xlarge 95.054
db.t4g.small 0.390
db.t4g.medium 0.780

Data Written

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.

China (Ningxia) Region ¥1.306/GB
China (Beijing) Region ¥1.306/GB

Snapshot Storage

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:

China (Ningxia) Region ¥0.157 per GB-month
China (Beijing) Region ¥0.180 per GB-month

Pricing Examples

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 China (Ningxia) Region. 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.

Your total charges are calculated as follows:
On-Demand Node Charges
(1 Primary + 1 Replicas) * 1 = 2 total nodes
db.r6g.xlarge hourly pricing = ¥4.304/hour
2 nodes * ¥4.304 = ¥8.608/hour
Data Written Charges
Data Written = 25GB * 3% (throughput update every hour) = 0.75 GB/hour
Data Written pricing = ¥1.306/GB
0.750 GB/hour * ¥1.306/GB = ¥0.9795/hour
Snapshot Storage Charges
Day 1: Free of charge for snapshot storage
Day 2: Snapshot storage space for 25 GB = 25 GB * ¥0.157 per GB-month= ¥3.925/month
¥3.925/730 hours in month = ¥0.005/hour
Total Charges
Node Charges = ¥8.608/hour
Data Written Charges = ¥0.9795/hour
Snapshot Storage Charges = ¥0.005/hour
Total = ¥8.608+ ¥0.9795 + ¥0.005 = ¥9.5925/hour

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 China (Beijing) Region 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:

On-Demand Node Charges
(1 Primary + 1 Replica) *2 =4 total nodes
db.r6g.xlarge hourly pricing = ¥5.942/hour
4 nodes * ¥5.942 = ¥23.768/hour
Data Written Charges
MemoryDB charges only for the writes. So for 50,000 transaction per second with 20% writes and 80% read, you only need to pay for 20% of 50,000 (10,000 transactions per second).
Hence, it is 10,000 transactions per second * 100 bytes * 60 * 60 = 3.6 GB/hour
Data Written pricing = ¥1.306/GB
3.6 GB * ¥1.306/GB = ¥4.702/hour
Snapshot Storage Charges
Day 1: Free of charge for snapshot storage
Day 2: Snapshot storage space for 50 GB = 50 GB * ¥0.180 per GB-month= ¥9/month
¥9 / 730 hours in month = ¥0.012/hour
Total Charges
Node Charges = ¥23.768/hour
Data Written Charges = ¥4.702/hour
Snapshot Storage Charges = ¥0.012/hour
Total = ¥23.768+ ¥4.702+ ¥0.012= ¥28.482/hour