EC2 Instance Not Managed by SSM
There is no managed path to patch or reach the instance, so administration falls back to SSH keys and manual updates.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable Systems Manager management on EC2 instance.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- EC2 Instances on AWS
- The fix, by hand
- EC2 → Instance the resource → Actions → Security → Modify IAM role → attach a profile with AmazonSSMManagedInstanceCore.
- Verify Systems Manager → Fleet Manager lists the instance as Online (5-10 min).
- Confirm by opening Session Manager → Start session against the instance.
- Close port 22 inbound on the security group. Session Manager replaces SSH.
- Enroll in Patch Manager with a baseline matching your maintenance window.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-154- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.