Free Tier
Amazon MemoryDB Free Tier is only available in the Amazon Web Services China (Ningxia) Region operated by NWCD. The Free Tier includes 750 hours of MemoryDB on t4g.small instances per month and 20GB of data per month for 2 months.
Overview
Amazon MemoryDB is a Valkey-, Redis-compatible, durable, in-memory database that delivers ultra-fast performance and Multi-AZ durability. With Amazon MemoryDB, 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 free in Amazon Web Services China (Ningxia) region
As part of the Amazon Web Services Free Tier, you can get started with MemoryDB for free in Amazon Web Services China (Ningxia) region. Upon signup, new MemoryDB customers receive 750 hours of MemoryDB on t4g.small instances and 20GB of data per month free for 2 months.
Pricing Glossary
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
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.
MemoryDB for Valkey - China (Ningxia) Region
|
Instance Type
|
Pricing (Ningxia)
|
|---|---|
|
db.r6g.large
|
1.506
|
|
db.r6g.xlarge
|
3.013
|
|
db.r6g.2xlarge
|
6.025
|
|
db.r6g.4xlarge
|
12.049
|
|
db.r6g.8xlarge
|
24.098
|
|
db.r6g.12xlarge
|
36.147
|
|
db.r6g.16xlarge
|
48.195
|
|
db.t4g.small
|
0.2
|
|
db.t4g.medium
|
0.398
|
MemoryDB for Valkey - China (Beijing) Region
|
Instance Type
|
Pricing (Beijing)
|
|---|---|
|
db.r6g.large
|
2.079
|
|
db.r6g.xlarge
|
4.159
|
|
db.r6g.2xlarge
|
8.317
|
|
db.r6g.4xlarge
|
16.634
|
|
db.r6g.8xlarge
|
33.268
|
|
db.r6g.12xlarge
|
49.904
|
|
db.r6g.16xlarge
|
66.538
|
|
db.t4g.small
|
0.273
|
|
db.t4g.medium
|
0.546
|
Data Written – MemoryDB for Valkey
|
Instance Type
|
Pricing
|
|---|---|
|
First 10TB / Month
|
¥0/GB |
|
Over 10TB / Month
|
¥0.26/GB
|
MemoryDB for Redis OSS - 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
|
MemoryDB for Redis OSS - 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
|
Reserved Nodes
Reserved nodes provide a significant discount off the ongoing hourly usage rate for the node(s) you reserve in one-year or three-year terms. With reserved nodes, you can choose to:
Pay low hourly charges with no upfront payment
Make a one-time, partial upfront payment with lower hourly charges
Pay all upfront with no hourly charges
China (Ningxia) Region
|
Partial Upfront
|
1-Year Term
|
1-Year Term
|
3-Year Term
|
3-Year Term
|
|---|---|---|---|---|
|
Memory Optimized Reserved Nodes
|
Upfront (Ningxia)
|
Hourly (Ningxia)
|
Upfront (Ningxia)
|
Hourly (Ningxia)
|
|
db.r6g.large
|
6123.897
|
0.699
|
13566.787
|
0.516
|
|
db.r6g.xlarge
|
12253.488
|
1.399
|
27146.189
|
1.033
|
|
db.r6g.2xlarge
|
24504.129
|
2.797
|
54286.07
|
2.066
|
|
db.r6g.4xlarge
|
49005.411
|
5.594
|
108565.834
|
4.131
|
|
db.r6g.8xlarge
|
98007.975
|
11.188
|
217125.36
|
8.262
|
|
db.r6g.12xlarge
|
147013.386
|
16.782
|
325691.194
|
12.393
|
|
db.r6g.16xlarge
|
196015.95
|
22.376
|
434250.72
|
16.524
|
|
|
|
|
|
|
|
All Upfront
|
1-Year Term
|
1-Year Term |
3-Year Term |
3-Year Term |
|
Memory_Optimized_Reserved_Nodes
|
Upfront (Ningxia)
|
Hourly (Ningxia)
|
Upfront (Ningxia)
|
Hourly (Ningxia)
|
|
dbr6glarge
|
12059.366
|
0
|
25437.726
|
0
|
|
dbr6gxlarge
|
24129.946
|
0
|
50899.104
|
0
|
|
dbr6g2xlarge
|
48254.285
|
0
|
101786.382
|
0
|
|
dbr6g4xlarge
|
96502.963
|
0
|
203560.938
|
0
|
|
dbr6g8xlarge
|
193000.32
|
0
|
407110.05
|
0
|
|
dbr6g12xlarge
|
289503.283
|
0
|
610670.988
|
0
|
|
dbr6g16xlarge
|
386000.64
|
0
|
814220.1
|
0
|
|
|
|
|
|
|
|
No Upfront
|
1-Year Term
|
1-Year Term |
3-Year Term |
3-Year Term |
|
Memory Optimized Reserved Nodes
|
Upfront (Ningxia)
|
Hourly (Ningxia)
|
Upfront (Ningxia)
|
Hourly (Ningxia)
|
|
db.r6g.large
|
0
|
1.463
|
0
|
1.119
|
|
db.r6g.xlarge
|
0
|
2.927
|
0
|
2.238
|
|
db.r6g.2xlarge
|
0
|
5.853
|
0
|
4.476
|
|
db.r6g.4xlarge
|
0
|
11.705
|
0
|
8.951
|
|
db.r6g.8xlarge
|
0
|
23.409
|
0
|
17.901
|
|
db.r6g.12xlarge
|
0
|
35.114
|
0
|
26.852
|
|
db.r6g.16xlarge
|
0
|
46.818
|
0
|
35.802
|
China (Beijing) Region
|
Partial Upfront
|
1-Year Term
|
1-Year Term
|
3-Year Term
|
3-Year Term
|
|---|---|---|---|---|
|
Memory Optimized Reserved Nodes
|
Upfront (Beijing)
|
Hourly (Beijing)
|
Upfront (Beijing)
|
Hourly (Beijing)
|
|
db.r6g.large
|
8455.59
|
0.965
|
18732.384
|
0.713
|
|
db.r6g.xlarge
|
16916.874
|
1.931
|
37477.382
|
1.426
|
|
db.r6g.2xlarge
|
33828.054
|
3.862
|
74942.15
|
2.852
|
|
db.r6g.4xlarge
|
67653.261
|
7.723
|
149877.994
|
5.703
|
|
db.r6g.8xlarge
|
135306.522
|
15.446
|
299755.987
|
11.406
|
|
db.r6g.12xlarge
|
202965.477
|
23.17
|
449646.595
|
17.11
|
|
db.r6g.16xlarge
|
270618.738
|
30.893
|
599524.589
|
22.813
|
|
|
|
|
|
|
|
All Upfront
|
1-Year Term
|
1-Year Term |
3-Year Term |
3-Year Term |
|
Memory Optimized Reserved Nodes
|
Upfront (Beijing)
|
Hourly (Beijing)
|
Upfront (Beijing)
|
Hourly (Beijing)
|
|
db.r6g.large
|
16651.008
|
0
|
35123.22
|
0
|
|
db.r6g.xlarge
|
33313.229
|
0
|
70270.092
|
0
|
|
db.r6g.2xlarge
|
66615.245
|
0
|
140516.532
|
0
|
|
db.r6g.4xlarge
|
133224.883
|
0
|
281021.238
|
0
|
|
db.r6g.8xlarge
|
266449.766
|
0
|
562042.476
|
0
|
|
db.r6g.12xlarge
|
399685.862
|
0
|
843087.366
|
0
|
|
db.r6g.16xlarge
|
532910.746
|
0
|
1124108.604
|
0
|
|
|
|
|
|
|
|
No Upfront
|
1-Year Term
|
1-Year Term |
3-Year Term |
3-Year Term |
|
Memory Optimized Reserved Nodes
|
Upfront (Beijing)
|
Hourly (Beijing)
|
Upfront (Beijing)
|
Hourly (Beijing)
|
|
db.r6g.large
|
0
|
2.02
|
0
|
1.544
|
|
db.r6g.xlarge
|
0
|
4.041
|
0
|
3.09
|
|
db.r6g.2xlarge
|
0
|
8.08
|
0
|
6.179
|
|
db.r6g.4xlarge
|
0
|
16.159
|
0
|
12.357
|
|
db.r6g.8xlarge
|
0
|
32.318
|
0
|
24.714
|
|
db.r6g.12xlarge
|
0
|
48.478
|
0
|
37.071
|
|
db.r6g.16xlarge
|
0
|
64.637
|
0
|
49.428
|
Data Written
|
China Region
|
Pricing
|
|---|---|
|
China (Ningxia) Region
|
¥1.306/GB |
|
China (Beijing) Region
|
¥1.306/GB
|
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
|
China Region
|
Pricing
|
|---|---|
|
China (Ningxia) Region
|
¥0.157 per GB-month |
|
China (Beijing) Region
|
¥0.180 per GB-month
|
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 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 25GB. On average, 3% of the data is updated every hour. You use a MemoryDB for Valkey 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 = ¥3.013/hour
2 nodes ¥4.304 = ¥6.025/hour
Data Written Charges
Data Written = 25GB 3% (throughput update every hour) = 0.75GB/hour
Data Written pricing = ¥0
0.750GB/hour ¥0/GB = ¥0/hour
Snapshot Storage Charges
Day 1: Free of charge for snapshot storage
Day 2: Snapshot storage space for 25GB = 25GB * ¥0.157 per GB-month= ¥3.925/month
¥3.925/730 hours in month = ¥0.005/hour
Total Charges
Node Charges = ¥6.025/hour
Data Written Charges = ¥0/hour
Snapshot Storage Charges = ¥0.005/hour
Total = ¥6.025+ ¥0 + ¥0.005 = ¥6.030/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 Valkey as your primary database. The application is read-heavy and has a total dataset size of 50GB 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 = ¥4.159/hour
4 nodes ¥5.942 = ¥16.637/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.6GB/hour
Data Written pricing = ¥0/GB
3.6GB ¥0/GB = ¥0
Snapshot Storage Charges
Day 1: Free of charge for snapshot storage
Day 2: Snapshot storage space for 50GB = 50GB * ¥0.180 per GB-month= ¥9/month
¥9 / 730 hours in month = ¥0.012/hour
Total Charges
Node Charges = ¥16.637 /hour
Data Written Charges = ¥0/hour
Snapshot Storage Charges = ¥0.012/hour
Total = ¥23.768+ 0+ ¥0.012= ¥16.649/hour