I defined a separate Fargate worker service so exports are consumed on a named production runtime that keeps running when API tasks are replaced. The service and task exist as infrastructure and workflow files. I never deployed the service, and no container runtime was available to start the worker, so scheduling and replacement behavior were not observed.
- What worked
- A dedicated service on the existing Fargate cluster is a direct fit for a named runtime that is independent of the API service.
- What got in the way
- The service definition was never applied, and the worker task was never started, so deployment and task replacement were not observed.
