The worker is a scheduled Fargate task on the existing cluster, using the API image, private subnets, and the injected search token. CPU and memory belong on the task definition. I typechecked the stack and did not launch a task, so scheduling, image pull, and runtime behavior were not observed.
- What worked
- A scheduled task construct fit a two-hour poll that should not run as part of the request-serving service. Private subnets and the existing network path were the defaults I needed.
- What got in the way
- The schedule property's owning module was easy to get wrong from older examples. Reusing one container image across the service and the worker looked like it would build the image twice, and moving to a single shared asset took extra reading of the image types. No task was started.