Skip to main content
Rightsizing · Low severity

Non-Nitro EC2 Instance, Migrate for Better Performance

Nitro instance types deliver higher network and EBS throughput at the same or lower price, so an older platform pays more per unit of work.

Sign inExplore the playground

Free to start. No card. The playground just needs your work email.

AWSprovider
Lowseverity
Savingswhere it shows up
Guidedfix, after a review

AWS

Found, explained, fixed.

Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.

01

Detect

ZopNight checks this automatically across AWS, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Migrate EC2 instance to a Nitro family. Where the saving can be proven it is priced; where it cannot, the finding says so.

03

Fix

After a guided review, where you confirm the change, ZopNight stops it, resizes it to the recommended tier, and starts it again, then checks the change took.

Applies to
EC2 Instances on AWS
The fix, by hand
  1. Identify the current-gen Nitro target in the same family: m4 → m7i, c4 → c7i, r4 → r7i, t2 → t3 or t4g (ARM). Skip m5/c5/t3. They are themselves older Nitro generations.
  2. Confirm ENA driver is installed in the AMI (Linux: ethtool -i eth0 should show ena; Windows: enable the ENA driver before swap).
  3. EC2 → select the resource → Stop → Actions → Instance settings → Change instance type → pick the target Nitro SKU → Start.
  4. Verify CloudWatch CPUUtilization + NetworkIn track the previous baseline; confirm application functionality.
  5. If in an ASG, edit the launch template + Instance refresh. Never mutate live ASG members.

ZopNight does this for you after a guided review.

Category
Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
Where it appears
The Savings tab of Recommendations, with every affected resource listed.
Rule ID
RC-187
Full reference

Non-Nitro EC2 Instance -- Migrate for Better Performance

Related checks

EC2 IMDSv2 Not RequiredAWSGPU Instance Low UtilisationAWSEC2 EBS Optimization Not EnabledAWSEC2 Instance Has a Public IP: Review If NeededAWSEC2 Instance Not Managed by SSMAWSEC2 RI Coverage Below 50%AWS

See the oversized resources 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.

Start freeExplore the playground

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.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·