Explain AWS NAT Gateway cost increases
Separate NAT Gateway-hour, processed-GB, and data-transfer charges so teams investigate the cost driver before changing network paths.
Find answers to common questions about cloud and AI costs.
Separate NAT Gateway-hour, processed-GB, and data-transfer charges so teams investigate the cost driver before changing network paths.
Review activation, historical gaps, and CUR 2.0 line-item values before using AWS resource tags to assign costs to teams.
Compare share-level utilization with snapshot storage in Azure Monitor before reviewing provisioned capacity. Keep account totals out of share-level decisions.
Match Compute Engine resource-based CUD scope to intended project coverage and verify shared reservation projects use the same Cloud Billing account before a move.
Review VM size suggestions against peak demand, compatibility and restart needs. Learn why estimated savings and empty recommendation lists need care.
Classify Cloud Run functions by documented version and console area before comparing costs. Keep pricing-family labels separate from API history and billed-SKU confirmation.
Check lifecycle rules before moving an individual Azure Block Blob out of Archive, and account for retrieval and early-deletion meters before approval.
Review AWS transfer usage types, Azure bandwidth categories, and Google Cloud network tiers before assigning a compute, storage, or network cost cause.
Compare retained Redshift Serverless usage with capacity and RPU-hour limits, then confirm whether each action warns, logs, alerts, or stops query processing.
Check whether an existing Azure Blob Inventory report covers retained versions and deleted objects, then compare its scope with Blob Capacity before planning storage changes.
Check BigQuery partition tiers and last-write timestamps before forecasting storage costs. Separate logical and billable bytes without treating metadata as a full bill.
Review AWS and Azure telemetry to separate application requests, model calls, retries, and evaluation activity before allocating AI spend.
Separate Cloud SQL charges from usage charts before choosing a cost change. Review one invoice month and include any separate MySQL enhanced-backup project.
Break down Amazon RDS costs by usage type so instance hours, storage, IOPS, backups, and transfer are reviewed separately before capacity changes.
Review BigQuery autoscale slot-seconds from the last day and compare reservation limits and slot sharing before asking an owner to change capacity.
Compare scoped AI spending with accepted business outcomes using a read-only worksheet that keeps retries, failed attempts and attribution gaps visible.
List SageMaker endpoints and notebook instances, compare endpoint activity, and ask owners which resources can become candidates for a cost reduction.
Review Cloud Storage versioning, soft delete, and locked retention settings before treating deletion as storage savings.
Check managed online deployment minimums and training-cluster node floors against workload needs, then use endpoint cost tags to prioritize owner reviews.
Compare Azure OpenAI token charges with hourly PTU capacity costs, including idle hours, model-specific sizing, reservation coverage and unused commitments.
Compare Azure reservation and savings plan scopes with eligible usage before widening access across an EA enrollment or MCA billing profile.
Compare model candidates on shared tasks, quality limits and response times. Use a read-only worksheet to estimate cost per accepted result from evaluation records.
Compare Cosmos DB partition utilization and 429 responses before a throughput cut, then use existing logs to identify keys with concentrated demand.
Review Standard and Premium profile fees, request counts, and transfer charges separately to identify which costs caching can reduce and which remain.