There is a point in many serverless platforms where a Step Functions workflow that once felt elegant starts to feel like a mini application platform of its own. I have seen this happen in teams that are doing many things correctly: they standardized orchestration, they improved visibility, and they moved fragile glue logic out of Lambdas. Then six months later, the workflow has 100+ states, a maze
Overview Let's get our hands dirty. This part covers the full setup and the actual demo: deploy PayLedger to both regions, wire up Route 53 failover, configure the Agent Space, inject three simultaneous faults, and walk through exactly what the agent found. Quick recap from Part 1: PayLedger is a demo payment ledger deployed to ap-southeast-1 (primary) and ap-northeast-1 (secondary) with Route 5
Want to keep Ubuntu updated? Run these commands on your PC via terminal, or create a .sh file and add the following commands: Bash If you don't know how to create the .sh file, no problem! Just navigate to the folder in your terminal and run the following: touch file.sh ----> creates the file nano file.sh -----> opens the file in the terminal Finally, add the previous commands to the file, press C