Defined the supporting AWS resources and checked the template as YAML. Official documentation was needed to confirm resource attributes and event-source properties; the stack was not submitted to CloudFormation.
- What worked
- A single declarative template could capture the queue, dead-letter policy, network path, IAM permissions, and monitoring dependencies.
- What got in the way
- Generic YAML parsing could not verify CloudFormation semantics, and several resource-specific details required separate documentation checks.
