Billing, Pricing, and Support: Cost Models and Plan Selection
The smallest domain, but the easiest place to lose easy marks, because the distractors sound financially sensible. Focus on when each pricing model is appropriate and what each support tier actually includes.
The purchasing options
- On-Demand - no commitment, highest unit price, right for spiky or short-lived workloads.
- Savings Plans - commit to a spend level for one or three years; Compute Savings Plans apply across EC2, Fargate, and Lambda, while EC2 Instance Savings Plans trade flexibility for a deeper discount on a specific family in a Region.
- Reserved Instances - one- or three-year commitment for steady-state compute or database capacity; convertible RIs allow family changes.
- Spot - spare capacity at steep discounts, interruptible with a two-minute warning; suitable for batch, rendering, and fault-tolerant jobs, never for a database that must stay up.
- Dedicated Hosts - physical servers for licensing or compliance requirements.
The Free Tier has three shapes: always-free allowances, twelve-month introductory allowances, and short-term trials.
Where the bill actually comes from
Inbound data transfer is generally free; outbound to the internet, cross-Region, and cross-Availability-Zone traffic is charged. Idle EBS volumes, unattached elastic IPs, and forgotten snapshots are classic overruns. Tagging resources by cost center makes the reporting usable.
Cost tooling
Pricing Calculator estimates before you build; Cost Explorer analyzes actual spend with forecasts; Budgets sends alerts or triggers actions against a threshold; the Cost and Usage Report is the most granular line-item export. AWS Organizations consolidated billing pools usage for volume discounts and shares Reserved Instance and Savings Plan benefits across accounts.
Support plans
Basic is free: account and billing help, documentation, and a limited set of core Trusted Advisor checks - no technical support. Developer adds business-hours email access to support associates and one named contact. Business adds 24/7 phone, chat, and email to engineers, faster response targets for production outages, the full Trusted Advisor check set, and access to Infrastructure Event Management for a fee. Enterprise On-Ramp and Enterprise add a Technical Account Manager and the fastest response commitments for business-critical systems, with Enterprise providing a designated TAM. Confirm current SLAs on the AWS site before quoting numbers.
Worked example
A rendering farm runs 24/7 but can tolerate interruption and checkpointing, while a customer database must never be interrupted. Assign Spot to the rendering fleet and a Savings Plan or Reserved capacity to the database. Both reduce spend, but only Spot accepts interruption - the differentiator is the workload's tolerance, not the discount.
Traps that cost marks
- Choosing Spot for stateful or latency-critical systems.
- Assuming Basic support includes technical troubleshooting or full Trusted Advisor checks.
- Expecting Business-tier support to include a designated TAM.
- Forgetting that inter-AZ and internet egress charges appear even when compute is fully discounted.