Wrote roles so the scheduler can start the task and pass its task role. The resource policy uses a wildcard revision suffix because access checks see the resolved revision even when RunTask is handed the family name. The policy was not evaluated in an account.
- What worked
- RunTask plus PassRole is the expected pair for a scheduled task, and a family-wide resource wildcard lines up with always running the latest active revision.
- What got in the way
- The resource string has to match the revision ARN that authorization resolves, not only the family ARN passed to the API. A mismatch would fail at start time. That behavior was inferred from docs and not tested.
