Practical cloud cost guidance for review and allocation work
Use these guides to review idle storage, compare cost measures correctly, and check whether tagging or labeling is ready for allocation analysis. Each item is read-only guidance, so it helps you decide what to inspect before any change.
Review EBS volumes in available status
Run a read-only inventory of EBS volumes in available status for the review scope defined by your AWS configuration. Treat the returned volumes as candidates for review, not automatic deletion targets.
This helps AWS operators and storage owners review volumes that are currently in available status. The result does not show whether a volume is unnecessary, billable, or safe to delete.
Read the guide, then run the describe-volumes inventory with the available status filter and review the volume ID, type, size, snapshot ID, and creation time fields.
Read guideRead FOCUS billed cost versus effective cost for GPU spend
Use EffectiveCost for accrual-based trends and allocation analysis, and BilledCost for invoice-aligned reporting. Verify currency treatment, provider scope, time window, and service identity before comparing GPU-oriented rows.
This matters for finance and FinOps teams that need consistent cost views. It helps avoid mixing invoice totals with adjusted cost views in the same analysis.
Read the guide, then compare BilledCost and EffectiveCost only after verifying the export's currency treatment and the documented scope and timing for the rows you are using.
Read guideCheck tag and label allocation readiness across three clouds
Record separate Azure, AWS, and GCP metadata signals before judging allocation readiness. Do not turn policy compliance or label inventories into a multi-cloud cost percentage by themselves.
This affects cost allocation owners who need comparable evidence across providers. It helps separate metadata hygiene from approved billing coverage.
Read the Azure Policy, AWS tag policy, and GCP project label guidance. Calculate a percentage only if approved billing export documentation defines comparable costs, metadata, scope, denominator, currency treatment, missing-value handling, and time windows for all three providers.
Read guideFind unattached Azure managed disks
List Azure managed disks whose managedBy property is null in the subscription you choose. Review the returned disk IDs before deciding whether any disk should be removed.
This helps Azure operators identify disks that may still incur charges after a VM is deleted. It is useful for storage cleanup reviews and cost control.
Read the guide, then run the Azure CLI disk listing in the intended subscription and review disks with a null VM reference before any deletion decision.
Read guide