Keep currencies separate in multi-cloud cost reports
Check cost denominations before combining cloud exports, choose billed or effective cost, and record a conversion policy that keeps totals traceable.
Find answers to common questions about cloud and AI costs.
Check cost denominations before combining cloud exports, choose billed or effective cost, and record a conversion policy that keeps totals traceable.
Review Cloud Storage lifecycle plans for unsupported transitions, retention blockers, and early-deletion charges before approving expected savings.
Check requested CPU, memory, storage and billable runtime for ECS Fargate tasks before estimating the cost of a sizing change.
Distinguish Stopped from Deallocated with a read-only Azure VM power-state check. Use PowerShell or ask an authorized colleague for the result.
Use AKS cost allocation and matching resource metrics to decide whether a cluster or namespace needs a capacity review, without treating allocated cost as proof of waste.
Compare a Compute Engine sizing recommendation with peak demand and memory evidence before approving a resize that could interrupt service or reduce performance.
Inventory available EBS volumes in one AWS account and Region, then verify ownership and retention before treating any volume as a removal candidate.
Separate GPU invoice totals from recognized consumption costs. Review FOCUS measures, period boundaries, currencies, commitments and workload mapping before reporting trends.
Check Azure tag policies, AWS compliance gaps, and GCP label scope before using metadata status to support a cross-cloud chargeback report.
List unattached Azure managed disks in one subscription, check when they became unattached, and review whether they are still needed before removal.