# Outdated ElastiCache engine version incurring extended support charges

Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/outdated-elasticache-engine-version-incurring-extended-support-charges

ElastiCache clusters continue running engine versions that have moved into extended support.

By: Kevin Talbierz

[Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) 

# Outdated ElastiCache Engine Version Incurring Extended Support Charges

The short version

ElastiCache clusters continue running engine versions that have moved into extended support.

[Kevin Talbierz](https://www.linkedin.com/in/kevin-talbierz/)

FinOps Manager @ Accor

AWS service

[AWS ElastiCache](https://www.pointfive.co/efficiency-hub/cloud-services/aws-elasticache)

Category

[Databases](https://www.pointfive.co/efficiency-hub/service-category/databases)

Reference

CER-0284

Type

Outdated Version

## Explanation

Why the waste happens and who it affects.

While the service remains functional, AWS charges an ongoing premium for extended support that provides no added performance or capability. These costs are typically avoidable by upgrading to a version within standard support.

## Billing model

The pricing dimensions that drive this cost.

ElastiCache applies additional extended support charges when clusters run engine versions outside standard support. These surcharges are added on top of normal node-hour pricing and accrue continuously while the cluster remains on an outdated version.

## How to detect

3 checks to find it in your estate.

- Review whether ElastiCache clusters are running engine versions no longer in standard support

- Assess whether extended support is required for compatibility or risk management

- Identify clusters that have remained on older versions beyond planned upgrade timelines

## How to fix

2 ways to remove the waste.

- Upgrade clusters to engine versions within standard support

- Establish periodic engine version reviews to avoid future extended support charges

## Documentation

Vendor references for pricing and configuration.

[https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/extended-support-versions.html](https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/extended-support-versions.html)

## Related inefficiencies

[Browse the library](https://www.pointfive.co/efficiency-hub)

- AWS ElastiCache  CER-0078

### [Outdated ElastiCache Node Type](https://www.pointfive.co/efficiency-hub/inefficiencies/outdated-elasticache-node-type)

Some ElastiCache clusters continue to run on older-generation node types that have since been replaced by newer, more cost-effective options. This can happen due to legacy templates, lack of version validation, or infrastructure that has...

Databases

- AWS ElastiCache  CER-0321

### [Suboptimal Cache TTL Strategy Causing Repeated Backend Execution](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-cache-ttl-strategy-causing-repeated-backend-execution)

Organizations deploy ElastiCache to reduce load on backend systems - databases, APIs, and compute layers - by serving frequently accessed data from fast in-memory storage. However, when Time-to-Live (TTL) values are misaligned with actual...

Databases

- AWS ElastiCache  CER-0146

### [Non-Graviton ElastiCache Node on Eligible Workload](https://www.pointfive.co/efficiency-hub/inefficiencies/non-graviton-elasticache-node-on-eligible-workload)

Many Redis and Memcached clusters still use legacy x86-based node types (e.g., cache.r5, cache.m5) even though Graviton-based alternatives are available. In-memory workloads tend to be highly compatible with Graviton due to their...

Databases

---
Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.