Used the existing load-balanced Fargate service construct to inject the billing secret into task environment and grant the execution role read access. Confirmed from types that task image options support secrets. The service was not deployed.
- What worked
- Secret injection on the task definition matched the need to pass a live key into the API without baking it into the image.
- What got in the way
- Had to confirm execution-role versus task-role permissions for secret pull; that was not obvious from the first construct usage.
