> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrade to Exit Extended Support

> Upgrade databases, clusters and caches past end of standard support to stop paying AWS extended support charges.

When an engine or Kubernetes version reaches the end of standard support, AWS keeps running it but adds an extended support charge on top of the normal price. nOps finds resources billed for extended support in Amazon RDS (including Aurora), DocumentDB, Neptune, EKS, OpenSearch Service and ElastiCache, and shows that charge as the saving from upgrading.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Compute |
| **Service** | Amazon DocumentDB, Amazon EKS, Amazon ElastiCache, Amazon OpenSearch Service, Amazon RDS |
| **Action** | Upgrade |
| **Effort** | Medium |
| **Restart needed** | Yes |
| **Can be rolled back** | No |
| **Analysis window** | Last 30 days |
| **Source** | nOps |

## Why it matters

Extended support charges grow in later years and can exceed the cost of the resource itself. Upgrading removes the charge entirely and keeps you on a version that gets security fixes.

## How nOps finds it

nOps reads the last 30 days of billing for extended support charges on each resource. A resource is flagged when the charge was at least \$5 over those 30 days, it was billed on at least 25 of them, and it was still billed in the last 2 days of data. The saving is the full extended support charge for the 30 days.

## Before you start

A target version in standard support, a tested upgrade path for your application, and a maintenance window.

## How to implement

1. Find the current version and the versions you can upgrade to. For RDS: `aws rds describe-db-engine-versions --engine ENGINE --engine-version VERSION --query "DBEngineVersions[0].ValidUpgradeTarget"`.
2. Test the upgrade on a copy or a non-production environment, including your application.
3. Upgrade in a maintenance window:
   * RDS, Aurora, DocumentDB, Neptune: **Modify** the instance or cluster and choose the new engine version.
   * EKS: update the control plane (`aws eks update-cluster-version`), then the node groups and add-ons.
   * OpenSearch Service: **Actions → Upgrade** on the domain.
   * ElastiCache: modify the cluster to a newer engine version, or upgrade Redis OSS to Valkey.
4. Update the version in Terraform or CloudFormation so the next deployment does not try to change it back.

## Risks and considerations

* Major version upgrades can need application changes. Test first.
* Engine upgrades restart the database or nodes, so plan for downtime or use blue/green deployments where available.
* Most upgrades cannot be reversed in place. Take a snapshot first so you can restore the old version if needed.

## FAQs

> [accordion] Is the saving the whole cost of the database?
>
> No. Only the extended support charge stops. The normal instance, storage and I/O charges stay the same.

> [accordion] Can I upgrade ElastiCache Redis OSS to Valkey instead?
>
> Yes. Moving to a supported Valkey version also ends Redis OSS extended support, and Valkey is priced lower.

## Related

* [Upgrade Cloud SQL to Exit Extended Support](https://help.nops.io/inform/supported-recommendations/upgrade-cloud-sql-to-exit-extended-support)
* [Upgrade ElastiCache Redis OSS to Valkey](https://help.nops.io/inform/supported-recommendations/upgrade-elasticache-redis-oss-to-valkey)
* [Migrate RDS Instance to Graviton](https://help.nops.io/inform/supported-recommendations/migrate-rds-instance-to-graviton)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.