AWS cost playbook

AWS Cost Optimization Hub vs CloudPrune: Recommendations Are Only Step One

Users want a centralized list of AWS savings recommendations across accounts and regions.

Prepared by Zeptrix CloudPrune ยท Updated July 24, 2026

Add impact analysis to AWS recommendations
Read-only scan No AWS changes made Impact and rollback notes

The cost signal

Users want a centralized list of AWS savings recommendations across accounts and regions. CloudPrune can differentiate on impact analysis, workflow, tenant-friendly onboarding, and recommendations saved outside the AWS console.

Review method
Read-only evidence first, followed by owner review, rollback planning, and post-change validation.
Reference
New Cost Optimization Hub centralizes recommended actions AWS blog

How to verify manually

  1. Open AWS Billing and Cost Explorer to confirm the service driving the spend.
  2. Use the AWS console view for the affected service to identify candidate resources.
  3. Run a read-only AWS CLI inventory command and export the resource IDs before changing anything.
  4. Compare age, attachment, traffic, retention, and recent usage signals before deciding on cleanup.

Impact and rollback

  1. Classify whether the action can affect production traffic, data retention, compliance, or incident response.
  2. Prefer dry-run review first. For storage deletion, create or verify a snapshot/export when rollback matters.
  3. Schedule changes with an owner and a validation window. Stop if the blast radius is unclear.
  4. Keep the previous configuration or snapshot reference until post-change metrics are stable.

How CloudPrune helps

CloudPrune starts read-only, scans AWS evidence, stores the recommendation, and shows savings context with risk, downtime, impact analysis, and safer execution steps.

Add impact analysis to AWS recommendations

Related CloudPrune resources