Follow the request/data flow through the architecture.
Work through each concept and mark it understood. This unlocks the knowledge check.
ML-powered alerts when spend deviates from expected patterns.
Why it matters
Catches runaway spend before the invoice arrives.
When to use it
Enable for all production accounts. Set thresholds based on historical baselines.
Gotcha (exam trap)
False positives cause alert fatigue — tune thresholds and add suppression rules for expected spikes (e.g., monthly batch jobs).
A realistic main.tf for this mission. Read it top to bottom — it mirrors the concepts above.
# Cost Anomaly Detection & Budgets
# BleepxCloud — FINANCE · Intermediate
# Realistic starter — adapt names, regions and CIDRs to your environment.
terraform {
required_providers { aws = { source = "hashicorp/aws", version = "~> 5.0" } }
}
provider "aws" {
region = "eu-west-1" # pick a region close to users / data-residency rules
}
# FinOps: mandatory cost-allocation tags on every resource.
locals {
common_tags = {
Project = "bleepx-cloud"
Domain = "finance"
Mission = "cost-anomaly-detection"
ManagedBy = "terraform"
CostCenter = "REPLACE_ME"
}
}
data "aws_caller_identity" "current" {}
# This mission is design-led — model the services below as resources:
# - cost-anomaly
# - budgets
# - cur
# - alerts
Finish the walkthrough above to unlock the check.
Bleepx skills build on each other. Continue your learning path across Query, Lab, and Cloud.