Left the carrier request on the existing Fargate service and only extended the task role so the API can reach the new tables and secrets. The fan-out stack stayed separate so later consumer deploys do not rebuild that image. The service was not deployed.
- What worked
- The existing service definition accepted additional task permissions while the request path stayed a single row write and the fan-out functions stayed outside the service network.
