Skip to main content
Rightsizing · Low severity

RDS Dev/Test Burstable Opportunity

Burstable classes price a low baseline with credit-funded peaks, which fits dev/test load and costs less than a class sized for a peak that rarely arrives.

Sign inExplore the playground

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

AWSprovider
Lowseverity
Savingswhere it shows up
Manualfix, steps written out

AWS

Found, explained, handed over.

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: Move the dev/test RDS instance to a burstable class. Where the saving can be proven it is priced; where it cannot, the finding says so.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
RDS Instances on AWS
The fix, by hand
  1. Confirm this is a non-production database with low, variable CPU. Burstable (db.t*) classes earn CPU credits at a baseline and suit bursty dev/test workloads.
  2. Check CloudWatch CPUUtilization over the last 30 days: the average should sit well below the burstable threshold with no sustained peaks that would exhaust CPU credits.
  3. Open RDS → Databases → select → Modify → DB instance class → pick the same-size db.t4g equivalent (Graviton burstable, the current-generation RDS burstable family; db.t3 is still supported but no longer the default).
  4. Apply during the next maintenance window; the instance reboots once.
  5. Monitor CPUCreditBalance after the switch to confirm the workload has credit headroom for occasional bursts.

These are the steps the finding carries in the product.

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-033
Full reference

RDS Dev/Test Burstable Opportunity

Related checks

RDS Instance Publicly AccessibleAWSRDS Instance Not Using Multi-AZAWSIdle RDS Instance, No ConnectionsAWSRDS Instance Right-sizingAWSRDS RI Coverage Below 50%AWSRDS Reserved Instance OpportunityAWS

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·