Specified a Scheduler cron that starts one batch task and then stops, with two retries and a two-hour event-age window. Docs for the ECS target were needed to place the public-IP flag inside network configuration and to pass a task-definition ARN with no revision so the latest active revision is used. The schedule was never created in an account.
- What worked
- The schedule resource can express a UTC cron, a Fargate launch type, network placement, and a bounded retry policy in one target. That is the right control plane for a nightly job that must stay off the web process.
- What got in the way
- The revisionless ARN, the nested network block, and the fact that authorization still evaluates the concrete revision are easy to misread. Those rules came from a docs search and were not confirmed by creating a schedule.
