Amazon ElastiCache pricing

Key terms

Data stored: You pay for data stored in ElastiCache Serverless billed in gigabyte-hours (GB-hrs). ElastiCache Serverless continuously monitors the amount of data stored in your cache, sampling multiple times per minute, and calculates an hourly average to determine the cache’s data storage usage in GB-hrs. Each ElastiCache Serverless cache is metered for a minimum of 1 GB of data stored (for ElastiCache for Memcached and ElastiCache for Redis OSS). You can further optimize costs on ElastiCache Serverless for Valkey with 33% lower pricing and 90% lower minimum data storage of 100 MB compared to other supported engines. 

ElastiCache Processing Units (ECPUs): You pay for ElastiCache Serverless requests in ElastiCache Processing Units (ECPUs), a unit that includes both vCPU time and data transferred. Reads and writes require 1 ECPU for each kilobyte (KB) of data transferred. For example, a GET command that transfers 3.2 KB of data will consume 3.2 ECPUs. Commands that require additional vCPU time or transfer more than 1 KB of data will consume proportionally more ECPUs.

Minimum metered data storage: 100 MB per cache for ElastiCache Serverless for Valkey and 1 GB per cache for ElastiCache for Memcached and ElastiCache for Redis OSS.

You can create a node-based ElastiCache cluster by choosing a cache node type and the number of cache nodes. A node is the smallest building block of an ElastiCache cluster. For information on which node size to use, see supported node types and choosing your node size.

Using on-demand nodes allows you to pay for memory capacity by the hour with no long-term commitments. When using on-demand nodes, you are billed hourly from the time a node is launched until it is terminated. Each partial node-hour consumed will be billed as a full hour.

ElastiCache reserved nodes or instances (RIs) provide a significant discount off the ongoing hourly usage rate for the node(s) you reserve in one-year or three-year terms. The one-time fee is non-refundable. With reserved nodes, you can balance the amount you pay upfront with your effective hourly price with one of the following options:

• No Upfront: pay low hourly charges with no upfront payment and receive up to 48.2% discount compared to on-demand. For every hour in the term, you are charged an hourly rate that is lower than on-demand.
• Partial Upfront: make a one-time, partial upfront payment with lower hourly charges and receive up to 52% discount compared to on-demand. For every hour in the term, you are charged an hourly rate that is lower than on-demand and lower than No Upfront hourly rate.
• All Upfront: pay all upfront and receive up to 55% discount compared to on-demand. There are no additional usage fees for the hours used during the term.

All reserved nodes are size flexible so you can apply your reserved node discounts across different sized nodes beyond the size specified in your reservation. With flexible reserved nodes, you don't need to commit to a specific node size when purchasing a reservation, reducing the overhead of capacity planning and enabling you to right-size your clusters as your workloads and capacity needs change.

Reserved nodes require no change to how you use ElastiCache. When computing your bill, AWS will automatically apply reserved node rates first to minimize your costs. A node hour will only be charged the on-demand rate when the total number of nodes you run that hour exceeds the number of applicable reserved nodes you own. For example, if you own 3 reserved nodes with the same node type in a given Region, AWS checks each hour to see how many total nodes you have running that match those parameters. If it is 3 or less, you will be charged the reserved node rate for each node running that hour. If more than 3 are running, you will be charged the on-demand rate for the additional nodes.

If you have existing Redis OSS reserved nodes and want to upgrade to Valkey, your Redis OSS reservations automatically apply to Valkey nodes in the same instance family and Region. Because Valkey is priced 20% lower than Redis OSS, if you have an existing Redis OSS reserved node, you can upgrade your cache to the Valkey engine and continue receiving your reservation benefits with 20% more value. To learn more, visit our ElastiCache reserved node documentation.

Note: Reserved nodes are not available with ElastiCache Serverless.

* RI monthly fees are the average monthly payment over the course of the Reserved Instance term. For each month, depending on the ElastiCache instance type you run, the actual monthly payment will equal the actual number of hours in that month multiplied by the hourly usage rate, or the number of seconds in that month multiplied by the hourly usage rate divided by 3,600. The hourly usage rate is equivalent to the total average monthly payments over the term of the Reserved Instance divided by the total number of hours (based on a 365-day year) over the term of the Reserved Instance.

** RI effective hourly rate helps you calculate how much a Reserved Instance will save you over on-demand pricing. When you purchase a Reserved Instance, you are billed for every hour during the entire Reserved Instance term you select, regardless of whether the instance is running. The effective hourly price shows the amortized hourly instance cost. This takes the total cost of the Reserved Instance over the entire term, including any upfront payment, and spreads it out over each hour of the Reserved Instance term.

Extended Support allows you to continue using Redis OSS major versions after the community end-of-life. During this time, AWS provides fixes for critical security issues and bugs through patch releases giving you up to three years to upgrade to a new major version to meet your business requirements.

For provisioned instances on ElastiCache for Redis OSS, Extended Support is priced at an 80% premium for Year 1 and Year 2 and a 160% premium for Year 3. Extended Support pricing is also dependent on the AWS Region and calendar date. Refer to ElastiCache versions for Redis OSS EOL schedule for more details.

If you are running a cache.t4g.medium instance on ElastiCache version 5 for Redis OSS in the region AWS European Sovereign Cloud Region, it reached end of support on January 31, 2026. For the first two years of Extended Support (from February 1, 2026 to January 31, 2028), your hourly charges will consist of the On-Demand price of €0.0711 plus an Extended Support premium of 80% (calculated as €0.0711 × 80% = €0.0569), totaling €0.128 per instance hour. For the third year of Extended Support (from February 1, 2028 to January 31, 2029), while the On-Demand price remains at €0.0711, the Extended Support premium increases to 160% (calculated as €0.0711 × 160% = €0.1138), bringing the total hourly cost to €0.1849 per instance hour.

With ElastiCache, you can store backups at a rate of €0.0839 per GiB per month for all AWS Regions. There are no data transfer fees for creating a backup or for restoring data from a backup to a cache.

There is no charge for data transfer between Amazon Elastic Compute Cloud (Amazon EC2) and ElastiCache within the same Availability Zone (AZ). While standard EC2 Regional data transfer charges of €0.0086 per GiB in or out applies when transferring data between an EC2 instance and an ElastiCache node in different AZs of the same Region, you are only charged for the data transfer in or out of the EC2 instance.

Scenario: You are building a new application that requires a cache to store frequently accessed data from the database to improve application performance. You estimate that your average dataset size will be about 10 GB and an average request rate of 50,000 requests per second. You choose to deploy your workload in AWS European Sovereign Cloud Region.

Your total cache charges are calculated as follows:
Data storage charges with ElastiCache Serverless for Valkey
Average hourly data storage usage = 10 GB-hours.

Average hourly data storage charges:
10 GB-hours * = €0.0997/GB-hour = €0.997/hr.

ECPU charges
Since your workload is a caching use case, each request will consume 1 ECPU, assuming the average bytes transferred per request are less than 1 KB.

Average hourly ECPU usage = 50,000 requests/second * 3,600 seconds in an hour = 180,000,000 ECPUs.

Average hourly ECPU charges:
(180,000,000/1,000,000) *  €0.0027/ million ECPUs = €0.486/hr.

Total serverless charges
Data storage = €0.997/hr
ECPU charges = €0.486/hr
Total = €1.483/hour

Scenario: You are building an application that requires a cache that provides fast data access to enable a responsive, real-time user experience for an e-commerce website. You estimate that the application has a total cache dataset size of 10 GB in the idle state and grows to 100 GB during peaks for two hours during the day. Your application accesses this cache using Valkey and Redis OSS SET and GET commands to read and write objects of 500 bytes in size. You estimate that your typical request rate is 100,000 requests per second, with daily peaks of 1 million requests per second for two hours of the day. You choose to deploy your workload in AWS European Sovereign Cloud Region.

Decision: You choose to start building your application with ElastiCache Serverless for its simplicity. You can also choose to run the workload by configuring your own cluster using on-demand nodes. You compare the pricing of both options.

Serverless option
Your total charges are calculated as follows:

Data storage charges
Average hourly data storage usage = ((10 GB * 22 hours) + (100 GB * 2 hours))/24 hrs in a day = 17.5 GB-hours
Average hourly data storage charges:
17.5 GB-hours * €0.0997/ GB-hour = €1.745/hr.

ECPU charges
Since your workload comprises of Redis OSS SET and GET requests, and each request transfers 500 bytes, each request will consume 1 ECPU.
Average hourly ECPU usage = (100,000 ECPUs/sec * 3,600 seconds in an hour * 22 hours + 1,000,000 ECPUs/sec * 3,600 seconds in an hour * 2 hours)/24 hrs in a day = 630,000,000 ECPUs
Average hourly ECPU charges:
(630,000,000/1,000,000) * €0.0027/ million ECPUs = €1.701/hr

Data transfer charges
You access your serverless cache in the AZs you select, and thus do not incur any cross-AZ data transfer charges.

Total serverless charges
Data storage = €1.745/hr
ECPU charges = €1.701/hr
Total = €3.446/hour

On-demand nodes option
You design your cluster using r7g.xlarge nodes. To accommodate your peaks of 100 GB and 1 million requests per second, and keep a buffer of 20% for unpredictable peaks, you require six shards, each with 19.74 GB (75% of 26.32 GB) of available storage, with two nodes for high availability (when configuring your own cluster, ElastiCache recommends reserving 25% of the node’s memory for non-data use). You distribute your nodes evenly across two AZs to achieve high availability.

On-demand node charges
Cache.r7g.xlarge = €0.4145
Total = €0.4145 * 12 node cluster = €4.974/hr.

Data transfer charges
(100,000 requests/sec * 3,600 secs/hr * 22 hours + 1,000,000 requests/sec * 3,600 secs/hr * 2 hours)/24 = 630,000,000 requests/hr.
Data transferred = 630,000,000 requests/hr * 500 bytes/request = 293.36 GB/hr.
Approximately 50% of your data will cross AZs due to multi-AZ architecture
293.36 GB/hr * 50% * €0.0086/GB = €1.261/hr

Total on-demand charges
Node charges = €4.974/hr
Data Transfer charges = €1.261/hr
Total = €6.235/hr

Scenario: You have a straightforward database caching use case that uses Amazon ElastiCache for Memcached. You require high availability for your cache to avoid application performance degradation in case of a node or AZ failure. You estimate that the application has a total cache dataset size of 20 GB in the idle state and grows to 150 GB during peaks. Your application accesses this cache using Memcached set and get commands to read and write objects of 500 bytes in size. You estimate that your typical request rate is 100,000 requests per second, with daily peaks of 500,000 requests per second for two hours of the day. You choose to deploy your workload in AWS European Sovereign Cloud Region.

Decision: You choose to start building your application with ElastiCache Serverless for its simplicity. You can also choose to run the workload by configuring your own cluster using on-demand nodes. Since you require high-availability, you operate two ElastiCache for Memcached clusters and write to both clusters from your application. You compare the pricing of both options.

Serverless option
Your total charges are calculated as follows:

Data storage charges
Average hourly data storage usage = ((20 GB * 22 hours) + (150 GB * 2 hours))/24 hrs in a day = 30.83 GB-hours
Average hourly data storage charges:
30.83 GB-hours * €0.149/GB-hour = €4.594/hr.

ECPU charges
Since your workload comprises of Memcached set and get requests, and each request transfers 500 bytes, each request will consume 1 ECPU.
Average hourly ECPU usage = (100,000 ECPUs/sec * 3,600 seconds in an hour * 22 hours + 500,000 ECPUs/sec * 3,600 seconds in an hour * 2 hours)/24 hrs in a day = 480,000,000 ECPUs
Average hourly ECPU charges:
(480,000,000/1,000,000) * €0.004/ million ECPUs = €1.920/hr

Data transfer charges
You access your serverless cache in the AZs you select, and thus do not incur any cross-AZ data transfer charges
Total serverless charges
Data storage = €4.594/hr
ECPU charges = €1.920/hr
Total = €6.514/hour

On-demand nodes option
You design your cluster using r7g.xlarge nodes. To accommodate your peaks of 150 GB and keep a buffer of 20% for unpredictable peaks, you require seven shards, each with 26.32 GB of available storage. You will require a total of 14 nodes to create two clusters for high availability.

On-demand node charges
Cache.r7g.xlarge = €0.4145
Total = €0.4145 * 7 node cluster * 2 clusters = €5.803/hr.

Data transfer charges
(100,000 requests/sec * 3,600 secs/hr * 22 hours + 500,000 requests/sec * 3,600 secs/hr * 2 hours)/24 = 480,000,000 requests/hr.
Data transferred = 480,000,000 requests/hr * 500 bytes/request = 223.51 GB/hr.
Approximately 50% of your data will cross AZs due to multi-AZ architecture
223.51 GB/hr * 50% * €0.0086/GB * 2 clusters = €1.922/hr.

Total on-demand charges
Node charges = €5.803/hr
Data Transfer charges = €1.922/hr
Total = €7.725/hr.

You work at a gaming company and your team manages a leaderboard. Your datastore size is 100 GB consisting of an average of 1.2 KB objects. You use Valkey SortedSet data structure to maintain your leaderboard and your average request rate is 500,000 requests per second. Each request from your workload averages three times the vCPU time of a SET or GET request and transfers 1.2 KB of data. Hence, the average ECPU consumed by each request from your application is 3 ECPUs. You choose to deploy your workload in AWS European Sovereign Cloud Region. Your total charges are calculated as follows

Data storage charges
Average hourly data storage usage = 100 GB-hours

Average hourly data storage charges:
100 GB-hours * €0.0997/GB-hour = €9.97/hr.

ECPU charges
Average hourly ECPU usage = 500,000 requests/sec * 3 ECPUs/request * 3,600 seconds in an hour = 5,400,000,000 ECPUs

Average hourly ECPU charges:
(5,400,000,000/1,000,000) * €0.0027/ million ECPUs = €14.58/hr

Total serverless charges
Data storage = €9.97/hr
ECPU charges = €14.58/hr
Total = €24.55/hour

Use the AWS Pricing Calculator to calculate your ElastiCache cost in a single estimate based on locations, data transfer amounts, number of requests, and more.

• Engine Type:  Amazon ElastiCache for Valkey starts at €11/month and offers 33% lower price on ElastiCache Serverless and 20% lower price on ElastiCache node-based as compared to other supported engines.
• Serverless: Serverless caches help optimize costs by automatically scaling when needed, removing the need to provision capacity for peak demand.
• On-demand nodes: Clusters configured using on-demand nodes can help optimize costs for workloads that have predictable scaling needs.
• Reserved nodes: ElastiCache 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.
• Backup and restore: Storage space for backups is charged at a rate of €0.0839 per GiB per month for all AWS Regions.
• Data transfer: There is no charge for data transfer between Amazon EC2 and ElastiCache within the same AZ. While standard Amazon EC2 Regional data transfer charges apply when transferring data between an EC2 instance and an ElastiCache node in different AZs of the same Region, you are only charged for the data transfer in or out of the EC2 instance.

With ElastiCache Serverless, you are charged for cached data in GiB-hours and the number of ElastiCache Processing Units (ECPUs) used by your application. When designing your own cluster, pricing is per node-hour.

You pay for ElastiCache Serverless requests in ECPUs. The number of ECPUs consumed by your requests depends on the vCPU time taken and the amount of data transferred. Each simple read and write, like the Valkey and Redis OSS GET and SET commands or the Memcached get and set commands, requires 1 ECPU for each kilobyte (KB) of data transferred. For example, a GET command that transfers 3.2 KiB of data will consume 3.2 ECPUs.

Some Valkey and Redis OSS commands that operate on in-memory data structures can consume more vCPU time than a GET or SET command. ElastiCache calculates the number of ECPUs consumed based on the vCPU time taken by the command compared to a baseline of the vCPU time taken by a Redis OSS SET or GET command. For example, a SORT command that takes three times the vCPU time taken by a SET or GET command and transfers 2 KiB of data will consume 3 ECPUs.

If your command takes additional vCPU time and transfers more data than the baseline of 1 ECPU, then ElastiCache calculates the ECPUs required based on the higher of the two dimensions. For example, a ZADD command that takes two times the vCPU time taken by a SET or GET command and transfers 3 KiB of data will consume 3 ECPUs.

There is no charge for data transfer between Amazon EC2 and ElastiCache within the same AZ. When you create an ElastiCache Serverless cache you can choose the AZs where you want ElastiCache to create VPC endpoints. There are no cross-AZ data transfer costs when the EC2 instance accessing the cache is in the same AZ as the cache endpoints. If you access the cache from a different AZ, standard Amazon EC2 cross-AZ data transfer costs will apply. You are only charged for the data transfer in or out of the EC2 instance. There is no ElastiCache data transfer charge for traffic in or out of the VPC endpoint.

When you create a node-based cluster, your application directly connects to each cache node. While standard Amazon EC2 Regional data transfer charges apply when transferring data between an Amazon EC2 instance and an ElastiCache node in different AZs of the same Region, you are only charged for the data transfer in or out of the EC2 instance. There is no ElastiCache data transfer charge for traffic in or out of the ElastiCache node itself.

Standard data transfer rates apply for data transferred out from a Region.

Billing for ElastiCache Serverless caches commences as soon as the cache is available. Billing continues until the cache is deleted. ElastiCache Serverless caches are billed any time your cache is running in an “Available” or “Updating” state. If you no longer wish to be charged for your cache, then you must delete it to avoid being billed for additional usage

Billing for ElastiCache nodes commences as soon as the node is available. Billing continues until the node is terminated, which would occur upon deletion.

ElastiCache node hours are billed any time your node runs in an Available or Modifying state. If you no longer wish to be charged for your node, then you must terminate it to avoid being billed for additional node hours.

Your Redis OSS reservations automatically apply to Valkey nodes in the same instance family and Region. Because Valkey is priced 20% lower than Redis OSS, if you have an existing Redis OSS reserved node, you can upgrade your cache to the Valkey engine and continue receiving your reservation benefits with 20% more value. For example, if you purchased a reservation for 5 cache.r7g.2xlarge nodes for the Redis OSS engine, then when you upgrade your nodes to the Valkey engine, you can create a sixth cache.r7g.2xlarge node (20% more than 5 nodes) in the same region at no additional cost. 

Unless noted otherwise, ElastiCache prices exclude applicable taxes and duties, including VAT and applicable sales tax.