Back to all use cases
RedisSaaS

Paying a premium to stand still

Consider a SaaS company running Redis OSS 6 on Amazon ElastiCache. Standard support ends on 31 January 2027, and from 1 February 2027 each node carries an Extended Support premium of 80% of the on-demand node price in years one and two, rising to 160% in year three.

Challenge

ElastiCache enrols caches still on Redis OSS 6 in Extended Support automatically, and the premium is added to the price of every node on that version. The usual way out, upgrading inside ElastiCache, does not settle things for this team on its own. The product embeds Redis in a hosted offering for its customers, so Redis 7.4 and later do not fit: RSALv2 and SSPLv1 restrict offering Redis as a managed service to third parties. ElastiCache already bills Redis OSS 4 and 5 under Extended Support, and version 6 joins them in February 2027.

The team wants to stay on a BSD-licensed line until a Valkey migration has been tested against its own workload. It already runs the rest of its stack on self-managed Kubernetes, so a self-managed cache is not a new operating model, only one more service in it.

Environment

Redis OSS 6 on ElastiCache today, serving sessions and hot data for a multi-tenant SaaS product. Where those sessions hold payment data, the cache is in PCI DSS scope, which is easy to overlook for a component treated as just a cache.

The plan is to move to self-managed Redis 7.2, the last BSD-licensed Redis line and supported to 1 December 2029, and then to Valkey once it has been tested.

Options

Upgrade inside ElastiCache to ElastiCache for Valkey. No Extended Support premium, and AWS lists Valkey node prices below Redis OSS. For most ElastiCache customers this is the cheapest route, and moving off ElastiCache only to avoid the premium is rarely worth it on its own.

Pay for ElastiCache Extended Support. It buys time on Redis OSS 6 at a premium that doubles in year three.

Move to self-managed Redis 7.2, then Valkey. It fits teams that already run their platform themselves or need the same cache in environments ElastiCache does not reach, as in this scenario.

Approach

OSSeva starts with the numbers: the Extended Support premium on the team's own nodes against the cost of running Redis themselves, with the database support cost calculator covering the support side from their own figures. If self-managed wins, OSSeva supports the move to self-managed Redis 7.2 with signed, patched builds delivered as Docker images or apt and yum packages, running on your own Kubernetes or virtual machines, with Redis Cluster or Sentinel as before.

The later Valkey migration happens under the same contract, since OSSeva supports Valkey 7.2.x and 8.x. Valkey forked from Redis 7.2.4 and is wire-compatible at the fork point, so the test plan focuses on the commands and modules the product actually uses. Memory headroom is checked on each new instance before cutover, because RDB and AOF persistence under memory pressure is where Redis moves usually go wrong.

OSSeva Assure adds ACL, persistence and TLS reviews and a SOC 2 and PCI DSS attestation package. OSSeva Operate adds 24/7 monitoring, memory and eviction alerting, replication-lag monitoring and a 15-minute P1 incident response SLA.

What this delivers

The same BSD-licensed Redis without the Extended Support premium, operated where the rest of the platform runs, and a tested path to Valkey. Redis 7.2 stays supported to 1 December 2029, which gives the Valkey test plan room. If the calculator shows that moving to Valkey inside ElastiCache costs less, that is the answer. OSSeva for Redis is priced per instance cluster; book a discovery call for a quote.

Go deeper

Questions

Frequently asked questions

Book a 15-minute call

When does ElastiCache Extended Support start for Redis OSS 6?

Standard support for ElastiCache Redis OSS 6 ends on 31 January 2027. From 1 February 2027, caches still on version 6 are enrolled in Extended Support automatically and billed for it.

How much does ElastiCache Extended Support add?

A premium on top of the on-demand node price: 80% in years one and two, and 160% in year three, for every node still on the version.

What is the cheapest way out of ElastiCache Extended Support?

Usually upgrading inside ElastiCache, for example to ElastiCache for Valkey, which carries no Extended Support premium. Moving to self-managed Redis makes sense when there are other reasons to run the cache yourself.

Why stay on Redis 7.2 rather than a newer Redis?

Redis 7.2 is the last BSD-licensed Redis line and is supported to 1 December 2029. Redis 7.4 and later use RSALv2 and SSPLv1, with AGPLv3 added in Redis 8, and RSALv2 and SSPLv1 restrict offering Redis as a managed service to third parties.

Does OSSeva support Valkey after the migration?

Yes. OSSeva supports Valkey 7.2.x and 8.x, so the move from Redis 7.2 to Valkey happens under the same contract.

See every EOL & CVE-patching use case

All use cases
Book a call