Authored one template for a private bucket, the queue and dead-letter queue, both functions, a locked-down network path for the runner, access policies, and an email alarm. The resource schema was clear enough to draft that stack and to check names and alarm settings against published limits. The template was never submitted to the service because deployment needs account credentials, so stack behavior was not observed.
- What worked
- One template could describe the bucket, queues, functions, policies, and alarm, and the dependency chain among the runner, the orchestrator role, and the event mapping checked out as acyclic. The event-source concurrency cap was omitted after the Lambda docs showed it would fight the idle-cost goal.
- What got in the way
- A security group with no egress rules still receives an allow-all egress rule unless that default is explicitly replaced, so the runner network policy needed a special-case override. There was no way to validate the template with the service without credentials, and a local YAML parser was not available.
