Memory hook: Estimate before use, analyse after use, alert during use; none is an automatic spending cap.
Must remember
- Pricing Calculator estimates a proposed workload. Cost Explorer analyses spending and usage. Budgets alerts against configured thresholds and supports explicitly configured actions. Cost Anomaly Detection highlights unusual spending. Billing data can lag; alerts are not an instant hard limit.
- Cost and Usage Reports/Data Exports provide detailed billing records. Activate appropriate cost-allocation tags and build ownership conventions. Merely attaching a tag does not automatically make historical spend perfectly attributable.
- Organizations consolidated billing combines eligible usage and supports sharing of applicable discounts under the organisation's settings. Separate accounts preserve administrative boundaries; a consolidated bill is not shared IAM permission.
- Compare fixed on-premises spending with variable cloud charges using total cost: power, facilities, maintenance, staff, licences, networking and idle capacity. Rightsizing uses evidence to reduce excess resources; automation can reduce operational effort and forgotten-resource waste. BYOL requires compatible licence terms, not just technical installation.
- EC2 commitments, Spot and On-Demand serve different workload profiles. Storage prices can include request, retrieval and minimum-duration charges. Data transfer may cost money across AZs/Regions or to the internet. Public IPv4 and retained storage can bill independently of application traffic. Check the service's actual price dimensions.
- Current CLF guidance names Basic Support, Business Support+, Enterprise Support and Unified Operations. Compare technical access, response objectives and proactive assistance using the current plan matrix; old Developer/Business/Enterprise On-Ramp tables may be outdated. Do not memorise old prices or response times from an unversioned slide.
- AWS Health reports service/account events; Trusted Advisor recommends improvements. re:Post, documentation, whitepapers and Prescriptive Guidance support self-service learning. The Trust and Safety team handles reports of AWS-resource abuse. Professional Services, solutions architects and AWS Partners provide different kinds of technical assistance; Marketplace offers third-party software procurement and entitlement management.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Estimate a design that does not exist yet | Pricing Calculator. |
| Investigate last month's largest service cost | Cost Explorer, then detailed exports if needed. |
| Get notified about unusual spend | Cost Anomaly Detection; add budgets for planned thresholds. |
Traps
- A budget alert is not guaranteed to stop every resource.
- Savings on compute can be outweighed by storage, licences and transfer.
- Consolidated billing is not an access grant between accounts.
Active recall
1. Which tool answers what a proposed architecture might cost?
Pricing Calculator, with realistic quantities and assumptions.
2. Why can costs continue after stopping a VM?
Storage, snapshots, addresses and other independent resources may remain billable.
3. What should be checked before choosing a support plan?
The current plan features, technical support availability and response objectives relevant to the business.
4. Does adding a team tag necessarily categorise all previous bills?
No. Cost-allocation activation and historical availability need separate consideration.
5. Is the cheapest hourly rate always the cheapest solution?
No. Compare useful work completed, interruption handling, utilisation, transfer and operating effort.