Left the existing container service as a DynamoDB write and only passed it the WebSocket URL. Image asset staging for that service interacted badly with local synth output until the build context was narrowed.
- What worked
- Creating the fan-out resources before the service referenced the socket URL avoided a circular dependency, so the API did not need to publish events itself.
- What got in the way
- The service image context was the whole repository, so local synth output was copied into the image build until ignore rules were added.
