Skip to main content

Assessment quick reference

Structured quick-reference sections for prerequisites, installation, usage, and troubleshooting.

Before you start

  • Pick one cloud provider first (AWS, Azure, GCP, or OCI) to avoid overwhelming the team.
  • Use recent utilization and ownership data so the checklist reflects current waste patterns.
  • Treat savings estimates as directional prioritization, then validate with provider-native cost data before deleting resources.

This template works best as a workshop with engineering + platform + finance stakeholders reviewing the same checklist.

How to use the assessment

  1. 1Select a cloud provider and work through each category (compute, storage, network, PaaS, governance/process).
  2. 2Check items that match real waste signals in your environment and expand categories to inspect command examples.
  3. 3Review the implementation roadmap, metrics, and governance tabs, then export the report for execution tracking.

What the assessment produces

  • Estimated monthly and annual savings from identified shadow waste
  • Priority grouping (high / medium / low) for cleanup sequencing
  • An implementation roadmap with phased remediation steps
  • A downloadable markdown report for team planning and stakeholder review

Execution and validation notes

  • This page is an assessment framework; validate each cleanup candidate before making changes in production.
  • Use the included CLI/PowerShell examples as discovery steps, then apply your organization approval process for remediation.
  • Repeat the assessment monthly or after major migrations to catch newly introduced waste.

Do not delete resources solely from checklist matches. Confirm ownership, dependencies, and recent usage before remediation.

CloudCostChefs Shadow Waste Assessment

Comprehensive Multi-Cloud Cost Optimization Template

Uncover hidden waste across AWS, Azure, GCP, and OCI with our professional assessment framework. Identify shadow waste, prioritize actions, and implement systematic cost optimization.

Blaze
Blaze says:Don't try to fix everything at once. Start with the high-priority items on your biggest cloud provider -- knocking out just the top 5 checklist items typically recovers 60% of total waste.

AWS Assessment Progress: 0%

AWS Shadow Waste Assessment

Compute Ghosts (EC2 & Related Services)

0/6 items

Unused or underutilized compute resources bleeding your budget

Storage Specters (EBS, S3, Snapshots)

0/6 items

Orphaned storage resources accumulating costs silently

Network Phantoms (VPC, Load Balancers, IPs)

0/6 items

Network resources consuming budget without serving traffic

PaaS Poltergeists (Lambda, RDS, etc.)

0/6 items

Platform services running idle or underutilized

Your Potential Savings

0

Estimated monthly savings based on checked items

Annual Savings
$0
3-Year Savings
$0
ROI Potential
300-500%

Ready to Transform Your Cloud Kitchen?

Download your comprehensive assessment report and implementation guide to start optimizing today!

Visit CloudCostChefs

What to do next

Pick the path that fits where you are right now.

Trust & run-safety metadata

Key execution details for Shadow Waste Assessment so users know what they are downloading or running before they act.

Need verification guidance? See Security & Trust and Responsible Disclosure.

Review before runGitHub sourceExplicit + inferred metadata

Maintainer

CloudCostChefs

Last Updated

September 6, 2025

Last Tested

February 23, 2026

Minimum Access

Read access across the cloud platforms in scope for discovery; remediation steps may require elevated rights

Execution Type

GitHub-hosted multi-cloud assessment framework (commands + interactive planning workflow)

Version

2025-09-06

SHA256 Checksum

Not published yet (recommend adding checksum for downloadable files)

Verification Notes

Repository-linked assessment framework for identifying multi-cloud waste patterns. Review platform-specific commands, assumptions, and reporting methodology before using results in a remediation program.

Safe Usage Checklist

  • Run discovery commands with least privilege first and separate assessment from remediation execution.
  • Prioritize findings with platform owners before applying cleanup actions across multiple clouds.
  • Run in a non-production subscription/account/tenancy first and capture sample output before broader rollout.
  • Use least-privilege access. Current best hint from docs: Read access across the cloud platforms in scope for discovery; remediation steps may require elevated rights.

Quick start (fast path)

Minimal steps to safely get value from this tool without reading the entire page first.

Estimated time: 2-3 hours initial assessment + 30-90 days implementationDifficulty: BeginnerAccess: Review / read-only
  1. 1. Confirm scope and permissions

    Use least privilege and test in a non-production scope first. Minimum access hint: Read access across the cloud platforms in scope for discovery; remediation steps may require elevated rights.

  2. 2. Get the tool package / source

    View on GitHub and review the files before running.

    GitHub
  3. 3. Check prerequisites

    • ✅ Cloud console access with read permissions for comprehensive resource discovery across platforms
    • ✅ Basic CLI tools (AWS CLI, Azure CLI, gcloud, OCI CLI) for automated detection commands
    • ✅ Web browser for interactive assessment tool and report generation
  4. 4. Run safely and review output

    Repository-linked assessment framework for identifying multi-cloud waste patterns. Review platform-specific commands, assumptions, and reporting methodology before using results in a remediation program. Start with a small sample scope, then expand once results look correct.