Follow the request/data flow through the architecture.
Work through each concept and mark it understood. This unlocks the knowledge check.
A serverless orchestrator that runs workflows as visual state machines.
Why it matters
Adds retries, error handling and branching without custom glue code.
When to use it
Use for multi-step processes (ETL, approvals, ML pipelines).
Gotcha (exam trap)
Standard workflows bill per state transition; Express workflows suit high-volume, short-duration flows.
A realistic main.tf for this mission. Read it top to bottom — it mirrors the concepts above.
# Orchestration with Step Functions
# BleepxCloud — AWS · Advanced
# 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 = "step-functions"
ManagedBy = "terraform"
CostCenter = "REPLACE_ME"
}
}
data "aws_caller_identity" "current" {}
# This mission is design-led — model the services below as resources:
# - step-functions
# - state-machines
# - workflows
Bleepx skills build on each other. Continue your learning path across Query, Lab, and Cloud.