Skip to main content
Skip to main content
Still in beta — questions, comments or suggestions? aramb@aramb.dev

Billing, Pricing, and Support Review

Review of AWS pricing models, Free Tier, Cost Explorer, Budgets, pricing calculators, and support plans.

20 min
Intermediate

Learning Outcomes

By the end of this lesson, you will be able to:

  1. Match pricing models to appropriate use cases
  2. Estimate costs using AWS pricing tools
  3. Set up billing alerts and budgets
  4. Select appropriate support plans for needs

Quick Review: AWS Pricing Models

Micro-Activity

Match the Pricing Model to Its Characteristic

Connect each pricing approach to how it actually works.

Examples

Choose one, then match it on the right

Characteristics

Select an example first

0 of 6 matched so far.


Pricing Model Scenarios

ScenarioBest Pricing ModelWhy
Steady-state production databaseReserved InstancesPredictable workload, maximum savings
Batch processing jobs that can pauseSpot InstancesCost savings matter more than immediate completion
Development/testing environmentOn-Demand or SpotFlexible, no long-term commitment needed
Variable web trafficOn-Demand + Auto ScalingScale with demand, pay for what you use
3-year steady applicationSavings PlansFlexibility across instance types + discount

Micro-activity 1: Pricing Model Selection

Practice
1 / 3

A company runs a 24/7 database server that will be active for the next 3 years. Most cost-effective option?


Free Tier Review

Always Free (never expires):

  • Lambda: 1 million requests/month
  • CloudWatch: 10 custom metrics, 1 million API requests
  • DynamoDB: 25 GB storage, 200 million read/write units

12 Months Free (from signup):

  • EC2: 750 hours/month of t2/t3.micro
  • S3: 5 GB standard storage
  • RDS: 750 hours/month of db.t2.micro
  • CloudFront: 50 GB data transfer

Key principle: Free Tier is for learning and small projects, production workloads will exceed these limits.


Micro-activity 2: Free Tier Awareness

Practice
1 / 3

A startup launches their MVP and stays under Lambda 1M requests and DynamoDB 25GB. After 12 months, what happens to their bill?


Cost Management Tools

Micro-Activity

Match the Tool to Its Purpose

Connect each AWS cost tool to what it actually does.

Examples

Choose one, then match it on the right

Characteristics

Select an example first

0 of 6 matched so far.


Micro-activity 3: Cost Analysis Scenarios

Think about it

Your monthly AWS bill jumped from $200 to $800. Consider:

  1. Which tool do you open first to investigate?
  2. What dimensions would you analyze (service, region, time period)?
  3. What would you do if you discovered the increase was from:
    • An unterminated EC2 instance left running?
    • Unexpected data transfer charges?
    • A misconfigured CloudWatch log retention?

Map your investigation workflow to the AWS cost tools reviewed in this lesson.


Support Plans Review

PlanBest ForKey Features
Basic (Free)Learning, experimentingDocumentation, forums, health dashboard
Business Support+ ($29/month min)Production workloads24/7 phone/web/chat, <30-min response for critical
Enterprise Support ($5,000/month min)Mission-critical15-minute response, TAM, security incident response
AWS Unified OperationsDeep operational partnershipTAM + DSE, architecture guidance, event management

Key principle: Support plan should match business impact of downtime.


Micro-activity 4: Support Plan Selection

Practice
1 / 3

A solo developer learning AWS on evenings and weekends. Best support plan?


TCO (Total Cost of Ownership) Considerations

Cloud vs On-Premises:

FactorOn-PremisesCloud
Upfront costsHigh (hardware, facilities)Low (just first month's usage)
Operational costsHigh (power, cooling, staff)Included in service price
Scaling costsBuy new hardware (slow)Auto-scale (instant)
MaintenanceYour team manages everythingAWS manages infrastructure
Hidden costsPower, cooling, real estate, depreciationData transfer, storage growth

Key insight: Cloud TCO is usually lower when you factor in staff time, facilities, and opportunity cost of slow procurement.


Synthesis: Cost-Optimized Architecture

Think about it

You're designing a cost-effective architecture for a growing e-commerce site:

Current state: 2 EC2 instances (t3.medium) running 24/7, RDS db.t3.micro, CloudFront for assets, S3 for images

Growth projections: Traffic doubles every 3 months for the next year

Consider:

  1. When should you switch from On-Demand to Reserved/Savings Plans?
  2. How do you handle traffic spikes (sales events) cost-effectively?
  3. What monitoring prevents bill shocks?
  4. Which services provide "Always Free" benefits you can leverage?

Apply the pricing concepts from this lesson to develop a cost-optimization strategy.


Summary

ConceptKey Principle
On-DemandFlexibility, no commitment, highest per-hour cost
Reserved/Savings PlansSteady workloads, significant discounts for commitment
SpotInterruptible workloads, up to 90% discount
Free TierAlways Free (never expires) vs 12-Month Free (expires)
Cost ExplorerAnalyze past spending, identify trends
BudgetsSet thresholds, receive alerts before overspending
Support PlansMatch support level to business impact of downtime
TCOFactor in staff, facilities, opportunity cost, not just hardware

Best practices:

  • Use Pricing Calculator before deploying
  • Set up Budgets on day one
  • Monitor with Cost Explorer weekly
  • Right-size instances regularly
  • Use Reserved/Savings Plans for steady workloads

Final Review Quiz

Knowledge Check
1 / 3

A company has predictable, steady-state workloads running 24/7. Best approach to reduce costs?