Selected Fargate, matching the API, as the place the worker process runs after a redeploy. The task is defined to start the worker module from the same image. No task was launched in this session, so capacity, shutdown signals, and replacement behavior were not observed.
- What worked
- Reusing the API launch type kept the worker on managed tasks and made post-redeploy placement explicit in the service definition.
- What got in the way
- No Fargate task started, so runtime logs, stop behavior, and task replacement were not observed.
