Stop 10 · Cloud Platforms (AWS / GCP / Azure)Topics · 6/11

Cloud Cost Management

In short

Plenty of students have woken up to a surprise cloud bill from one forgotten server. At companies, keeping cloud spend in check is part of the DevOps job.

Cloud costs can spiral quickly without active management — right-sizing resources, using reserved/spot instances, and setting up billing alerts are basic but essential cost-control habits.

The mascot switches off a fan and lights in an empty room while glancing at a spinning electricity meter.

Think of it like this

The electricity meter

Leave the fan, lights and AC running in an empty room all month and the meter keeps spinning; the bill arrives anyway. Cloud resources are the same. A good habit is walking through the house switching off what nobody is using, before the bill shows up.

Watch it happen

A simple cost routine

Tag

Budget

Find waste

Right-size

Commit

1/5Tag every resource with owner, project and environment, so the bill can be split and questioned.

The big ideas

What you need to know

Alerts before anything else

Set a budget alert the day you create an account. It's the cheapest insurance in the cloud.

Stopped isn't free

A stopped VM still pays for its disks and any reserved IP. Delete what you don't need.

Spot for flexible work

Spare capacity sold cheaply, but it can be taken back at short notice. Fine for batch jobs and CI, not your only database.

Watch data transfer

Data leaving the cloud, and between zones, is billed. It's often the line item people forget.

See it in code

Walk through the code

hcl

1resource "aws_budgets_budget" "monthly" {2  name         = "monthly-cap"3  budget_type  = "COST"4  limit_amount = "20"5  limit_unit   = "USD"6  time_unit    = "MONTHLY"7 8  notification {9    comparison_operator        = "GREATER_THAN"10    threshold                  = 8011    threshold_type             = "PERCENTAGE"12    notification_type          = "FORECASTED"13    subscriber_email_addresses = ["you@example.com"]14  }15}

1/3A monthly cost budget with a limit of 20 US dollars.

A budget only alerts; it doesn't stop spending. You can also create one by hand in the AWS Billing console in a couple of minutes.

Save yourself the pain

Common mistakes

Oops

Leaving a practice NAT gateway or load balancer running after a tutorial.

Do this instead

These charge by the hour even with no traffic. Tear down labs with terraform destroy or delete the whole group.

Oops

Cutting cost by removing redundancy from production.

Do this instead

Trim waste first: idle resources, oversized instances, dev running all night. Then look at commitments.

Your mission

Set up your safety net

~20 min

Quick check

You stop an EC2 instance overnight. What are you most likely still paying for?

Go deeper

1Set up a billing alert on your free-tier cloud account before you risk an unexpected charge.
2Learn the difference between on-demand, reserved, and spot pricing models.
3Practice identifying an over-provisioned resource and right-sizing it.