Follow the request/data flow through the architecture.
Work through each concept and mark it understood. This unlocks the knowledge check.
AWS-native IaC in YAML/JSON, organized into stacks.
Why it matters
First-class AWS support with drift detection and rollback.
When to use it
Use when staying all-in on AWS and wanting native tooling/CDK.
Gotcha (exam trap)
Manual console changes cause "drift" — always change infra through the template, not by hand.
A realistic main.tf for this mission. Read it top to bottom — it mirrors the concepts above.
# CloudFormation: IaC from Zero
# BleepxCloud — AWS · Beginner
# 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 = "core"
Mission = "cloudformation-basics"
ManagedBy = "terraform"
CostCenter = "REPLACE_ME"
}
}
data "aws_caller_identity" "current" {}
# This mission is design-led — model the services below as resources:
# - cloudformation
# - yaml
# - stacks
# - outputs
Bleepx skills build on each other. Continue your learning path across Query, Lab, and Cloud.