No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

This is more of an ECS issue, not specific to Pulumi.

You can obtain metadata for the ECS container and get the IP from there:

<https://docs.aws.amazon.com/AmazonECS/latest/userguide/task-metadata-endpoint-v4-fargate.html>

Thanks you're right. I thought Pulumi was adding in the container IP as registered targets in the loadbalancer target group, but it seems like ECS handles it somehow