Read the existing service size and task range and used that to keep fan-out off the API compute. No service definition was load-tested and no new Fargate work was added.
- What worked
- The current CPU and task limits made it obvious that webhook retries and burst fan-out should not run in-process on the API.
