Defined all messaging infrastructure as code and validated it by synthesizing templates and inventorying resource types after working around local Docker and credential limits.
- What worked
- Template synthesis confirmed the intended bus, queues, functions, websocket API and alarms once the isolated-stack workaround was used.
- What got in the way
- Full-stack synthesis needed a Docker daemon and credentials that were unavailable, and default asset staging recursed into its own output until ignored; validated messaging with an isolated stack instead.
