New See exactly what you're overpaying AWS in under 60 seconds. Estimate your AWS savings →

ElastiCache Pricing (2026): Serverless, Node-Based & Savings

Amazon ElastiCache pricing depends on your deployment model, engine, AWS Region, cache capacity, request volume, and commitment choices. Node-based clusters bill for provisioned node-hours, while Serverless bills for stored data and ECPU processing. Compare total monthly costs, including replicas, data transfer, backup, and Reserved Node or Database Savings Plan eligibility.
Picture of Debesh Singh
Principal FinOps Practitioner

Debesh Singh

Principal FinOps Practitioner
November 2, 2026

·

19 min read
ElastiCache Pricing (2026): Serverless, Node-Based & Savings
In this article
Key takeaways
1
Node-based ElastiCache charges for running nodes, while Serverless bills for storage and processing.
2
Valkey offers lower comparable pricing than Redis OSS, subject to compatibility.
3
Serverless costs depend on GB-hours and ECPU consumption.
4
ElastiCache Reserved Nodes offer discounts of up to 55% on eligible node-based usage.
5
Database Savings Plans provide a separate, one-year commitment option for eligible Valkey workloads.

How does Amazon ElastiCache pricing work?

Amazon ElastiCache is AWS’s managed in-memory caching service for Valkey, Redis OSS, and Memcached.

The deployment model determines how the main usage charges are calculated.
Factor Node-based Serverless
Billing Node-hours GB-hours and ECPUs
Capacity Provisioned Automatically managed
Scaling Adjust node configuration Adjusts with demand
Reserved Nodes Eligible Not eligible
Typical fit Predictable workloads Variable workloads
Both models can incur additional charges depending on configuration.

Check AWS pricing for current regional rates.

How much does node-based ElastiCache cost?

Node-based ElastiCache charges for each running cache node. Your rate depends on the engine, instance type, and AWS Region.
Monthly node cost = Running nodes × Hourly rate × Hours

Example: Six Valkey nodes

AWS’s pricing documentation lists a cache.r7g.xlarge Valkey node rate of $0.3496 per hour in US East (N. Virginia).

For six nodes running continuously:
Component Calculation Cost
Hourly cluster cost 6 × $0.3496 $2.0976
Monthly node cost $2.0976 × 730 $1,531.25
Annual node cost $2.0976 × 8,760 $18,374.98
Illustrative node-based scenario. Charges exclude applicable additional costs.

Replicas are billable nodes. A cluster with three primaries and three replicas has six running nodes.

AWS bills partial On-Demand node-hours as full hours.

How much does ElastiCache Serverless cost?

ElastiCache Serverless pricing has two primary components:

Storage: Data stored over time, measured in GB-hours.

Processing: ElastiCache Processing Units (ECPUs) consumed by requests.

ECPUs account for processing and data transferred. Requests transferring more data or requiring additional processing can consume more ECPUs.

Example: Valkey Serverless pricing

AWS publishes the following US East (N. Virginia) reference rates:
Component Reference rate
Storage $0.084 per GB-hour
Processing $0.0023 per million ECPUs
Assume a workload stores an average of 10 GB and handles 50,000 requests per second, with each request consuming one ECPU.

Illustrative Serverless scenario only. It is not directly comparable to the six-node example.
Component Calculation Hourly cost
Storage 10 × $0.084 $0.840
Processing 180 million × $0.0023/million $0.414
Total $1.254
For a 730-hour month, the estimated charge is $915.42, excluding other applicable costs.

Actual ECPU consumption depends on request size and processing requirements.

Minimum storage charges

Engine Minimum metered storage
Valkey 100 MB
Redis OSS 1 GB
Memcached 1 GB
These minimums can affect small or lightly used caches.

Is Serverless cheaper than node-based ElastiCache?

Not necessarily.

Serverless can suit variable traffic, while node-based clusters may be more economical when demand is predictable.

For a fair comparison, match dataset size, request volume, peak demand, processing requirements, and availability configuration.

Use the AWS Calculator to model expected usage. For detailed Serverless calculations, see our Serverless pricing guide.

How does Valkey pricing compare with Redis OSS and Memcached?

Your engine affects both cost and compatibility.
Engine Pricing consideration Typical use
Valkey Lower comparable AWS rates Compatible Redis OSS workloads after validation
Redis OSS Higher comparable rates Existing Redis workloads
Memcached Separate pricing and simpler capabilities Basic key-value caching
AWS states that Valkey offers approximately 20% lower node-based pricing and 33% lower Serverless pricing than comparable Redis OSS configurations.

These differences do not guarantee equivalent reductions in total application spending. Validate client compatibility, engine versions, and migration requirements before switching.

What additional charges affect AWS ElastiCache pricing?

The base node or Serverless rate may not represent the complete bill.
Cost factor What to check
Replicas Additional provisioned nodes
Backup storage Applicable backup charges
Data transfer Network path and AWS transfer rules
Extended Support Older Redis OSS versions
Durability Optional synchronous-write premium
Data tiering Supported node types and storage economics
Global Datastore Cross-Region replication and transfer
Commitments Unused committed capacity

Data transfer

AWS does not charge for node-based ElastiCache traffic within the same Availability Zone. Other network paths may incur charges.

Serverless caches accessed through a VPC endpoint do not incur in-Region data-transfer charges. For public-endpoint traffic, AWS does not charge for data transfer in or out of the cache itself, but standard in-Region data-transfer charges apply to the application side.

For multi-Region architectures, estimate Global Datastore replication and cross-Region transfer costs separately.

Extended Support

Redis OSS versions 4 and 5 reached the end of standard ElastiCache support on January 31, 2026.

Affected clusters entered paid Extended Support beginning February 1, 2026.

AWS charges an 80% premium over the applicable On-Demand node rate for the first two years and 160% in the third year.

Reserved Node discounts do not reduce these premiums.

See the Support schedule for applicable dates.

Valkey durability

Valkey 9.0 offers optional durability for eligible node-based configurations.

Asynchronous writes have no additional durability premium, while synchronous writes add 18% to the standard node-hour price.

See AWS durability for eligibility.

Data tiering

Supported node-based ElastiCache configurations can use SSD-backed data tiering to increase storage capacity.

This may lower storage costs for suitable workloads, but accessing data from SSD can affect latency and throughput. Data tiering is not a Serverless pricing option.

How much can ElastiCache Reserved Nodes save?

ElastiCache Reserved Nodes provide discounted rates for eligible node-based usage under one-year or three-year commitments.

AWS publishes these maximum discounts:
Payment option Maximum advertised discount
No Upfront Up to 48.2%
Partial Upfront Up to 52%
All Upfront Up to 55%
Actual discounts depend on the eligible reservation offering.
Effective reserved hourly rate = Total commitment cost ÷ Commitment hours
A reservation can lower the effective rate, but its cost remains payable even when matching usage declines.

AWS supports size flexibility under applicable rules. Existing Redis OSS reservations can also apply to eligible Valkey nodes within the same instance family and Region.

For purchasing details, see our Reserved Nodes guide.

Can Database Savings Plans reduce ElastiCache costs?

Yes, for eligible Valkey usage.

AWS Database Savings Plans use a one-year, dollar-per-hour spending commitment with No Upfront payment rather than reserving specific node capacity.

Eligible ElastiCache usage includes supported Valkey Generation 7 and newer instances and Valkey Serverless. Redis OSS and Memcached are not listed as eligible ElastiCache usage.

Database Savings Plans and Reserved Nodes have different eligibility and flexibility rules. AWS does not apply both discounts to the same usage.

Before purchasing, review eligible database usage across the account because a Database Savings Plan can cover supported services beyond ElastiCache.

See Savings Plans FAQs for coverage rules.

Which ElastiCache pricing option should you choose?

Use the workload and commitment requirements to narrow your choice.
Option Eligible usage Term Flexibility Main risk
Serverless Supported cache engines No commitment Automatically adjusts capacity Processing and storage charges vary
Node-based On-Demand Supported node types No commitment Change or stop nodes Paying for provisioned capacity
Reserved Nodes Eligible node-based usage 1 or 3 years Limited by reservation rules Underused commitment
Database Savings Plans Eligible Valkey and other supported database usage 1 year Spend-based coverage across eligible services Unused committed spend
Choose Serverless when demand varies and its usage-based pricing fits your workload.

Choose On-Demand nodes when you need provisioned capacity without a long-term commitment.

Consider Reserved Nodes when eligible node usage is stable enough to justify the term.

Consider Database Savings Plans when you have predictable eligible Valkey or broader database spending and want spend-based flexibility.

Do not assume the highest advertised discount is automatically the lowest total cost.

How can you reduce your ElastiCache bill?

Focus on workload efficiency before purchasing commitments.
1

Right-size nodes. Review memory utilization, evictions, CPU pressure, and latency.

2

Evaluate Valkey. Identify Compare pricing and compatibility for Redis OSS workloads.

3

Review data tiering. Assess eligible configurations with large datasets and suitable access patterns.

4

Update engine versions. Plan upgrades where Extended Support charges can be avoided.

5

Check commitment coverage. Size purchases against stable eligible usage rather than peak demand.

How does Usage.ai help with ElastiCache savings?

Unused Reserved Node capacity and oversized commitments can erase the value of a good discount. Usage.ai helps teams analyze, purchase, and monitor eligible commitments, with conditional Cashback protection under applicable terms.

We now support Database Savings Plans automation for ElastiCache for Valkey, including Generation 7+ provisioned instances and Valkey Serverless. 

Coverage varies by commitment type and configuration. See the full published scope.

ElastiCache pricing checklist

Before finalizing your estimate, confirm:

AWS Region, engine, and deployment model

Node count or expected storage and ECPU consumption

Replication, availability, and network requirements

Backup, support, durability, and data-tiering costs

Existing Reserved Node and Savings Plans coverage

Expected workload changes

Total commitment cost and downside exposure

Final verdict

The best ElastiCache pricing option depends on workload demand, compatibility, and how much commitment risk your team can accept.

Compare equivalent configurations using current AWS rates, then evaluate discounts against realistic utilization rather than advertised maximum savings.
Before you commit
Estimate Your Next AWS Commitment Savings

Assess ElastiCache and AWS commitment coverage, eligible opportunities, and potential savings before purchasing.

Disclosure: We are Usage.ai, a cloud commitment-management provider. Examples use AWS-published reference rates and stated assumptions. Actual costs, savings, supported configurations, Cashback eligibility, and commercial terms vary. AWS pricing and eligibility can change; its current pricing documentation is authoritative.

Frequently asked questions

How much does Amazon ElastiCache cost per month?

Monthly costs depend on the engine, deployment model, Region, and usage. Node-based clusters charge for running nodes, while Serverless charges for storage and processing. Include additional applicable costs when estimating your bill.

Does ElastiCache charge for idle nodes?

Yes. Node-based ElastiCache charges for running provisioned nodes even when utilization is low. Serverless uses a different billing model with minimum metered storage amounts.

Is ElastiCache Serverless always cheaper?

No. Serverless may suit variable workloads, while node-based clusters can be economical for steady demand. Compare both using equivalent workload assumptions.

Can Reserved Nodes be used with ElastiCache Serverless?

No. Reserved Nodes apply to eligible node-based deployments. Supported Valkey Serverless usage may qualify for Database Savings Plans instead.

How do I calculate ElastiCache pricing?

For node-based clusters, multiply running nodes by the hourly rate and hours used. For Serverless, calculate GB-hours and ECPU charges. Add applicable additional costs and account for eligible discounts.

Share
Facebook
X
LinkedIn
Reddit
See your savings first
More from Usage.ai
Latest from our blogs