MySQL upgrade that cut about $10k a year in AWS costs
An outdated MySQL 5.7 database was quietly adding about $900 a month in AWS Extended Support fees. We planned and ran a safe upgrade to 8.0 around a live legacy application.
A medical equipment company runs its day-to-day operations on an internal legacy application hosted on AWS. The system could not simply be rewritten or paused — but its infrastructure had a clear cost leak.
The challenge
Part of the setup depended on MySQL 5.7 on RDS. AWS had moved that version onto paid Extended Support, which added roughly $900 every month for standing still.
A note on the fee itself, because many teams only discover it on an AWS bill: when a database version reaches the end of its standard support, Amazon RDS does not switch it off — it moves it onto Extended Support and starts charging extra for every hour it keeps running. For MySQL 5.7 this began in early 2024, and the same mechanism applies to other engines such as PostgreSQL. The fee is billed per vCPU-hour, so it scales with the size of your instances — and AWS roughly triples the rate after the first two years. Nothing about your application improves; you simply pay more each month until the database is upgraded.
The challenge was not the upgrade command — it was doing the upgrade safely around a legacy application with real users, real workflows and behaviour nobody wanted to break.
What we did
We treated it as a small modernisation project rather than a version bump — and the rehearsal proved that right:
- Reviewed the AWS and RDS setup and confirmed the Extended Support fees could be removed entirely by upgrading.
- Cloned the RDS instance and rehearsed the whole upgrade on a staging copy before touching production.
- The rehearsal caught a real blocker: an older application still ran alongside its newer replacement, and it depended on database constructs that failed on the upgraded MySQL. The old app simply could not work with 8.0 — quite possibly the reason the previous vendor never upgraded at all.
- Instead of forcing the upgrade through, we dedicated a sprint to bringing the newer application to full feature parity, gave the client’s team a couple of weeks to move across completely, and then stopped the old application — stopped, not deleted, while we watched that nothing was missing.
- With the old application retired, we cloned and upgraded the staging database once more, tested everything together, took a fresh backup, and upgraded production overnight — the system is internal and sits unused at night, so the risk window was minimal and a rollback path stayed ready.
Around the infrastructure work we kept supporting the application itself — issue investigation, quote and PDF fixes, shipping logic and other operational maintenance.
The outcome
About $900 a month in recurring AWS fees disappeared — roughly $10k a year — from one targeted piece of infrastructure work, with no rewrite and no disruption to the business.
Existing applications often hide recurring costs like this. Finding them is part of what a System Risk Check is for, and removing them safely is what our modernisation and upgrade work looks like.
More case studies
industry
Medical equipment
tech stack
AWS RDS, MySQL 5.7 → 8.0
service
Modernisation & Upgrades
Want results like these for your application?
Start with a System Risk Check — a fixed-price technical audit of your application with a written, prioritised report. The report is yours, whatever you decide next.
We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.
The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. We also use third-party cookies that help us analyse how you use this website, store your preferences, and provide the content and advertisements that are relevant to you. These cookies will only be stored in your browser with your prior consent. You can choose to enable or disable some or all of these cookies but disabling some of them may affect your browsing experience.