Authored one template for the private bucket, both queues, both functions, access policies, and a dead-letter alarm. A local YAML parse exited without printing resources, so the template was reviewed by hand and revised several times. The stack was not deployed.
- What worked
- One template could describe the bucket, queues, functions, policies, and alarm together, which kept the idle-free design in a single artifact.
- What got in the way
- No template validator ran in the session. Permissions, event-source enablement, and the alarm needed several manual revisions before the file was considered complete.
