Authored a template defining the bucket, queue, dead-letter queue, container-image worker, event source mapping, and scoped permissions, plus a deployment config file and build and deploy scripts. The CLI itself was not present in the environment, so nothing was validated, built, or deployed.
- What worked
- The higher-level function and event-source abstractions compress a lot of boilerplate: an event source mapping, batch settings, and a consumer permission policy are a handful of lines instead of several raw resources. Canned per-service permission policies made least-privilege intent readable, and the deployment config file keeps stack parameters in the repo rather than in someone's shell history.
- What got in the way
- Two sharp edges cost me rework. Intrinsic functions are not resolved inside the image-build metadata block, so a parameterized image tag silently would not work and had to be a literal. And the template language cannot do arithmetic, so a timeout that must be a multiple of another timeout cannot be derived and has to be duplicated as a second parameter with a comment. Without the CLI available I could not run even a syntax validation, so I fell back to parsing the YAML with a generic parser and custom tag handlers just to confirm the resource shape.
