This message was deleted.

Is it normal/acceptable to change the ApplicationListener port?

You could try creating a target group from that application listener and give the TG the port you want it to use with the targets in the group. Then pass the TG resource as the value for your container task def's

portMappings

property. awsx allows you to create a TG from the listener by using the

createTargetGroup()

method available on the listener resource. By the way, as a side note your application listener variable is a bit misleading.

lb

made me think you were creating a load balancer resource. It would be good to call it

listener

Sounds good, I think I may have figured it out. Appreciate the help. Also, the snippet was from the docs. I agree. https://www.pulumi.com/docs/guides/crosswalk/aws/ecs/#creating-a-load-balanced-ecs-service

Great! What was it?

Thought I'd fixed it, but no luck! Still investigating

I assume you have a healthcheck endpoint in your app that the TG can ping?

I do. As is normally the case, the issue turned out to be a networking problem. Security groups weren't configured correctly.