Home
›
Articles
›

The EC2 server nobody has patched since launch

The EC2 server nobody has patched since launch

By Ibi Hasanli

·

·

4 min read

The EC2 server nobody has patched since launch is often still running the product, which is why nobody wanted to touch it. The first job is to find out which operating system it is on, and whether that system is still in support. Once support ends, the vendor stops issuing standard security updates, so routine patching cannot close new holes.

Why an unpatched server gets riskier over time

A long-running EC2 instance can look fine for years, because the application still responds. The operating system underneath still ages.

Amazon Linux 2 reached its end of support on 30 June 2026, and Amazon's Linux 2 FAQs say it is no longer receiving standard security updates. Remaining on it, the same page says, carries increasing risk as new vulnerabilities are no longer patched. AWS recommends moving to Amazon Linux 2023, which it says is supported until June 2029.

The same clock runs on other common images. Canonical's Ubuntu release cycle gives long-term support releases five years of standard security maintenance. For Ubuntu 20.04 LTS, that standard term ended in May 2025; further coverage after that point is through Ubuntu Pro. Microsoft's Windows Server 2016 lifecycle lists an extended end date of 13 January 2027.

In support, and after support ends Still in support The vendor issues standard security updates Scheduled patching can apply those updates The job is to keep applying them, on an agreed window. Support has ended Standard security updates stop New holes are no longer patched by the vendor The job is a planned move to a supported OS and a current image. Patching an unsupported operating system does not bring vendor support back.
In support, scheduled patching can apply vendor updates. After support ends, plan a move to a supported OS and a current image.

What an AMI is, and why an old image matters

An AMI, or Amazon Machine Image, is the base image a server is built from. In AWS's words, it is the image that provides the software required to set up and boot an EC2 instance, including the operating system.

If that image was taken from an older generation, every instance launched from it starts behind. Patching the running server can close gaps in a supported OS. It cannot turn an unsupported AMI into a supported one, and it cannot jump a major version on its own. You need a current image, a plan to move, and a way back if the move fails. A backup restore test belongs in the same conversation as a patch window.

What managed patching looks like in practice

Managed patching is not a one-off login to run an update.

  • Inventory: which instances you have, which operating system each one runs, and which AMI it was built from.
  • Support check: whether that operating system is still receiving standard security updates from the vendor.
  • Scheduled patching: if it is in support, apply updates on an agreed window, with a named person who can approve a reboot.
  • A move, if support has ended: plan a replacement on a supported OS and a current AMI, tested before the old server is switched off.

AWS Systems Manager Patch Manager can automate scans and, if you choose, install missing patches, and report which nodes are out of date. It does not, AWS says, support upgrading major versions of operating systems, such as Windows Server 2016 to Windows Server 2019. That work is a migration, and should be planned as one.

What managed patching looks like 1. Find what is running The operating system, and the AMI it was built from 2. Check support Is the OS still receiving standard security updates? 3. If it is in support Schedule patches, agree the window and who approves a reboot 4. If support has ended Plan a move to a supported OS and a current AMI A major version change is a migration, not a routine patch. Get that in writing.
Start with the OS and the AMI, then a support check. In-support systems get a scheduled window; out-of-support systems need a written migration.

What else a managed AWS arrangement should include is covered in what managed AWS hosting actually includes, and what's still on you. How the care fee sits beside the AWS invoice is in why your AWS bill and your management fee are two different bills.

What to get in writing

Before you pay someone to "keep it patched", get these points on paper.

  • What is patched, and how often: the operating system, and whether applications are in scope.
  • The window and the reboot: when patches run, and who can approve a restart.
  • Out-of-hours cover: only if it is written into the retainer. Ordinary enquiries are not the same thing.
  • Unsupported systems: whether a move to a supported AMI is included, or quoted separately.
  • Rollback: that backups exist, and whether restores are tested before a patch window or a migration.

How Eight Mile takes on an inherited server

Our infrastructure and cloud work includes designing, building and running infrastructure on AWS. Infrastructure support can include patching, backups and on-call cover, through a monthly arrangement with agreed coverage. Customers keep the cloud accounts; we work with access to them.

If we did not build the system, work starts with a review of what it does, its fragile areas and running costs, then a written plan. That can include mapping an old server, rebuilding its setup as code, and proving the replacement before switching off the original. Support is a separately agreed retainer. Billing starts only once a written scope and price are agreed. If the login still sits with a freelancer, start with leaving a freelancer with your AWS root login. If the application is the inherited part, see what to check before you inherit a custom app.

Can you name the operating system, say whether it is still in support, and point to the last successful patch? If the EC2 server nobody has patched since launch is still carrying the business, that is the work to start.

If you want that checked and a written plan on an AWS account you own, talk to an engineer. Tell us what is running and when it was last updated, if you know.

AWS
Infrastructure

Leaving a freelancer with your AWS root login

Leaving a freelancer with your AWS root login is a risk even after a good build. How to take back control with named IAM, MFA and a handoff.

·

4 min read

Infrastructure
Cloud

Moving off the server under the desk

Moving off the server under the desk: stage a move to managed hosting or cloud you own — without a big-bang rewrite.

·

3 min read

Infrastructure
Cloud

Cloud bill went up and nobody can say why

Cloud bill went up and nobody can say why: usually orphaned resources, missing tags, or one shared account. Fix ownership first.

·

3 min read

AWS
Infrastructure

AWS vs managed hosting for a small SaaS

AWS vs managed hosting for a small SaaS: when simple platforms fit, and when owned cloud, IAM and infra in git win.

·

3 min read

AI
Decision models

Jev vs Laya

Jev vs Laya for UK tech leads: when to call TypeSafe's hosted decision API and when to self-host the open-weight Laya model on your own infrastructure.

·

4 min read

Security
Cyber Essentials

Cyber Essentials for small businesses

A plain-English guide to Cyber Essentials for small businesses, covering what the scheme checks and when a contract will ask for it.

·

4 min read

Security
Audit

Security audit vs penetration test

Security audit vs penetration test: when to review config first, when a buyer needs a pentest, and usual order for SaaS.

·

3 min read

Security
Git

Secrets in git repository

Secrets in git repository history outlive a deleted file. Rotate first, then stop the next temporary commit.

·

3 min read

Backups
Disaster recovery

Backup restore test

A backup restore test proves copies work on a clock you can live with. Untested backups are hope with a green tick.

·

3 min read

Infrastructure
Cloud

One person knows how to deploy it

If one person knows how to deploy it, you have a person, not a process. Fix ownership, access, and a path the team can run.

·

3 min read

Infrastructure

AWS CDK Infrastructure

How infrastructure as code with AWS CDK improves delivery, governance, scalability, and long-term cloud maintainability.

·

7 min read

Infrastructure

Terraform Basics

Learn how Terraform turns infrastructure into repeatable code, from providers and state to planning safe changes.

·

2 min read

Infrastructure

What is DevOps?

Bridging the Gap Between Development and Operations for Faster, Reliable Software Delivery

·

4 min read