This message was deleted.

sparse-intern-71089

01/05/2021, 11:00 AM

This message was deleted.

brave-planet-10645

01/05/2021, 11:38 AM

Can you do it using the base AWS provider rather than the AWSX one? The main difference is that the container definition in the task definition needs to be a string rather than an object but that should work I think. If you look at my example in the github issue you referenced, you'll see that it outputs the container definition so you can see what it looks like

thousands-london-78260

01/05/2021, 12:35 PM

I'll give it a shot. But was hoping that I could somehow manually attach the targetGroups after the resources have been created?

straight-librarian-43739

01/05/2021, 6:54 PM

I’ve been looking for a workaround here too. Would love to hear what you find out. I’m gonna try using the AWS provider as well, will report back.

straight-librarian-43739

01/06/2021, 6:49 PM

I tried this using the

aws

provider instead, and it still doesn’t like two listeners on a

aws.ecs.Service

. I get the following error:

InvalidParameterException: Not allow to have same target groups in a service.

straight-librarian-43739

01/06/2021, 6:49 PM

(one listener/tg works fine)

thousands-london-78260

01/08/2021, 8:49 PM

Eventually gave up on using awsx for this and just used the normal aws. It's a bit more work in that you need to create all the service accounts etc, but I was doing that anyways.

56 Views

Open in Slack

Previous Next

Pulumi Community

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.