Hi all, just reposting what I had in the server channel. I hope someone can help. We’re deploying an ECS agent as a container into a Fargate ECS cluster. As far as I can tell, the load balancer etc are all configured sensibly - they use the same settings as other containers which work. Prior to the agent starting, we can see logs on Cloudwatch (for instance, if we send a broken command), but once it’s launched, there is nothing. The container health fails, and the task goes into a health check loop. We’re seeing lots of messages telling us that a task failed to load the image, but again, we know the image is accessible and is being loaded initially, because we can see logs from it when we change the command in the Dockerfile. I want to understand more about what’s going on here. We have no NAT or internet gateway configured, due to security restrictions, which we know will prevent the agent from communicating with Prefect Cloud, but we would expect some sort of message to tell us so. Could someone explain why we’re getting the messages about ECR? Is the agent trying to load additional instances of itself into the cluster?

Hi @Ben Collier, I’ll join the server thread

Thanks Kevin!