A CloudFormation template captured the complete messaging topology, encryption, subscriptions, redrive configuration and access policies. It passed static linting but was not submitted to AWS.
- What worked
- The resource model expressed the fan-out topology and queue policies in one reviewable deployment artifact.
- What got in the way
- Without credentials, stack creation and service-side template validation could not be observed.
