I used the rule and container-task target types as the higher-level way to run a recurring ingest task. They described role, network, and security-group wiring. The stack typechecked. I did not publish a rule or watch an invocation.
- What worked
- The task-target types made IAM and network wiring explicit, which avoided hand-writing those settings on a low-level schedule resource.
- What got in the way
- No rule was published, so schedule drift, retry behavior, and task launch failures were not observed.
