This message was deleted.

sparse-intern-71089

05/07/2021, 7:56 PM

This message was deleted.

red-match-15116

05/07/2021, 8:11 PM

I’m not sure about your specific question, but the aws-ts example in the repo shows it set up slightly differently… https://github.com/pulumi/examples/blob/master/aws-ts-hello-fargate/index.ts Perhaps that could be helpful?

proud-art-41399

05/07/2021, 8:18 PM

There are multiple examples showing usage of load balancers I have tried, e.g. • https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/lb/ • https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/ecs/ But none of them handles the case when the task port differs from the listener port. Such example would be really helpful

proud-art-41399

05/07/2021, 8:23 PM

Looking at the code (https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/index.ts), the

elasticloadbalancingv2

from your example is just an alias to

lb

so it's equal to the example from

pulumi/awsx

docs I posted. That's what I also tried without success :-/

red-match-15116

05/07/2021, 8:26 PM

Yeah hopefully someone else can jump in and help you out, this isn’t my area of expertise 🙂

👍 1

proud-art-41399

05/08/2021, 4:42 AM

Got some sleep and it was worthy. I found out where the problem was. The load balancer's security group didn't have an outbound rule allowing traffic to the target group / health check port. I think this should be carried out by the package, though.

26 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.