This message was deleted.
# aws
s
This message was deleted.
r
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?
p
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
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 :-/
r
Yeah hopefully someone else can jump in and help you out, this isn’t my area of expertise 🙂
👍 1
p
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.