On a server that faces the public internet, an outdated SSH daemon is one of the first things an attacker checks. For this AWS hardening task I upgraded and validated OpenSSH on a live EC2 instance — bringing the daemon to a current, patched version and confirming, not assuming, that remote access kept working afterward.
The approach: stage the upgrade carefully on a production box where a mistake means losing your own access, then verify the running version and a clean reconnect before walking away. That validation discipline is the difference between a hardening step and an outage.
The result is an EC2 server running patched, current SSH with verified secure access intact — one piece of the broader AWS infrastructure hardening I deliver for clients.
Stack: AWS EC2, Linux, OpenSSH, server hardening. Delivered as a client engagement on Fiverr.