New Savings Proposals: approve, test and roll back cost changesLearn more Sign in|Talk to a cloud engineer
Product tourGet a demo

Upgrade before extended support fees start

Find every database, cluster and runtime on a version that is losing standard support, see what extended support will add each month, and send the upgrade to Jira once.

Get a demoJira integration
What you're watching
  1. 1
    Read the three numbers

    23 resources on EOL versions across 4 accounts, $2,960/mo in extended-support fees if nothing changes, and the next deadline in 34 days.

  2. 2
    Create a ticket for PostgreSQL 12

    catalog-db adds $980/mo on extended support. FINOPS-219 is created, and the button turns into a link so nobody files it twice.

  3. 3
    Bundle the other two into an Epic

    Kubernetes 1.28 on platform-eks and Node.js 16 on image-resizer go into Epic FINOPS-220, with 2 issues linked.

Who does thisData platform engineer, with the engineering manager planning the sprintWhat you getEvery upcoming deadline filed in Jira once, with its cost and owner attached.
AWS + AzureRDS, EKS, ElastiCache, OpenSearch, Lambda, MSK, AKS, Functions and more
$/moextended-support cost priced per resource
Jiraticket per finding, or one Epic for a group
Weeklyemail digest of upcoming deadlines

End of life arrives as a bill and an audit note

Extended support fees start on a date you can see coming. So does the end of security patches.

Cost

A version runs out of standard support

What usually happens: RDS keeps the database running on paid extended support, and the per-vCPU-hour surcharge shows up before anyone planned the upgrade.

How CloudLens resolves it: catalog-db shows PostgreSQL 12 ending standard support in 34 days, and the +$980/mo it would add.

Resolved
Security

Runtimes without patches

What usually happens: A Lambda function on a deprecated runtime keeps working, so it stays off everyone’s list until a vulnerability lands.

How CloudLens resolves it: image-resizer on Node.js 16 is listed as deprecated today, with the upgrade path next to it.

Resolved
Ops

Upgrade tickets filed twice, or never

What usually happens: The same deadline gets filed by three people, or by nobody.

How CloudLens resolves it: Create a Jira ticket per finding or an Epic for the group. Once it exists, the button becomes a link to it.

Resolved

How Dev planned three upgrades in one sprint

A Monday digest turned into three owned tickets and one fewer extended-support charge.

DPDev PatelData platform engineer, Lumora Retail

Lumora Retail is a fictional company. The people, names and numbers are sample data.

    1
    Mon 09:00

    The weekly EOL digest arrives

    Three items: PostgreSQL 12 on catalog-db in 34 days, EKS 1.28 on platform-eks in 51 days, and Node.js 16 on image-resizer, already deprecated.
    2
    Mon 09:20

    Sorts by extended-support cost

    catalog-db would add $980/mo, and the platform-eks control plane would cost six times as much on extended support. Those two go first.
    3
    Mon 09:35Epic created

    Bundles them into one Jira Epic

    One Epic in the FINOPS project with three linked issues, each with the version, the deadline and the cost filled in.
    4
    Mon 09:40

    The buttons turn into links

    When Sofia opens the same findings that afternoon, she sees links to the tickets instead of Create buttons, so nothing is filed twice.
    5
    Wed 17:00

    Tests the upgrade on staging

    Following the migration plan on the finding, Dev upgrades the staging copy of catalog-db to PostgreSQL 16 first.
    6
    Next Mon−$980/mo

    The digest has two items left

    catalog-db is on PostgreSQL 16 and drops off the list, along with its $980/mo of extended-support cost.
Extended support fees coming up?

Scan your estate for end-of-life versions

Get a demo

From a vendor support date to a ticket with an owner

See what waiting will cost

When standard support ends, some engines keep running on paid extended support. CloudLens shows the monthly surcharge for each resource and the migration plan that avoids it.
  • Monthly surcharge per resource
  • Migration plan and savings
  • Deadline in days
What you're watching
  1. 1
    See the fee start

    catalog-db's monthly cost gains a red extended-support layer right after the Standard support ends line.

  2. 2
    Read the 12-month total

    Doing nothing adds $11,760 in extra fees over the next 12 months.

  3. 3
    Toggle Upgrade before deadline

    The red layer disappears and $980/mo is saved. The four-step PostgreSQL 16 plan is tracked in FINOPS-219.

Who does thisData platform engineer, with the finance managerWhat you getA priced reason to upgrade catalog-db now, with the plan already in Jira.

Every engine and runtime on one timeline

Support windows for AWS and Azure databases, Kubernetes, caches, search, streaming and serverless runtimes, with the versions you actually run marked against today.
  • AWS: RDS, EKS, ElastiCache, OpenSearch, Lambda, MSK
  • Azure: AKS, Functions, MySQL, PostgreSQL, Cosmos DB
  • Your versions highlighted
What you're watching
  1. 1
    Read the AWS support windows

    Green bars are standard support and orange bars are extended, per version, from RDS PostgreSQL down to Amazon MSK.

  2. 2
    Find your versions on Today

    Blue dots mark what you run, such as PostgreSQL 12, EKS 1.28 and Node.js 16 on Lambda.

  3. 3
    Switch to Azure

    The same timeline covers AKS, Functions, Azure Database for MySQL and PostgreSQL, and Cosmos DB for MongoDB.

Who does thisPlatform lead planning upgrades by quarterWhat you getEvery version you run, placed against its support dates on one axis.

File each upgrade once, and keep reminding owners

How the Jira integration syncs
Create a Jira ticket for one finding or an Epic for a group. Once a ticket exists the button becomes a link, so nobody files it twice. A weekly email digest keeps upcoming deadlines in front of the owners.
  • Ticket per finding or an Epic
  • Existing tickets remembered
  • Weekly EOL digest
What you're watching
  1. 1
    The digest lands Monday at 08:00

    The platform team gets 4 deadlines in the next 150 days, worth $1,555/mo in extended-support charges.

  2. 2
    Read each deadline

    PostgreSQL 12 on catalog-db adds $980/mo and Kubernetes 1.28 adds $365/mo. Redis OSS 6.2 adds $210/mo, and Node.js 16 gets no patches.

  3. 3
    Act from the email

    Open EOL & Deprecation to see the details, or create an Epic bundle straight from the digest.

Who does thisPlatform team owners, read by the engineering managerWhat you getUpcoming deadlines stay in front of owners every week, each with a price.

Upgrades planned by quarter, not by incident

Deadlines with prices

A support date gets attention when it comes with the amount it will add every month.

Straight into Jira

Findings become tickets or epics in the project you choose, and stay linked to the finding.

A maintained catalog

Engine and runtime support windows across AWS and Azure, kept current for you.

Unsupported software on exposed resources Recommendations

EOL & Deprecation questions

On AWS: EKS, ElastiCache (Redis OSS, Memcached, Valkey), Elasticsearch and OpenSearch, Lambda runtimes, MSK, and RDS for MySQL, MariaDB and PostgreSQL. On Azure: AKS, Cosmos DB for MongoDB, Functions runtimes, and Azure Database for MariaDB, MySQL and PostgreSQL.

From each provider’s published extended-support pricing, applied to the size and number of the resources you run.

No. CloudLens remembers the ticket linked to each finding and shows a link to it instead of creating another.

Ready to see CloudLens in action?

Connect a read-only AWS role or Azure service principal. We'll walk you through your bill, your security graph and the first things worth fixing.