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

Is it the same issue? Same error, different issue, maybe? The issue you linked says it was resolved in TF AWS provider 2.43.0. The current version of the Pulumi provider is built from version 3.33.0 of the TF AWS provider...

<https://aws.amazon.com/blogs/aws/new-host-based-routing-support-for-aws-application-load-balancers/>

2.43.0 of the provider was adopted in release 1.17.0 of the Pulumi provider. So long as you're using something newer, you should be ok...

What version of the aws provider are you using? Could it be very old?

Do you have two condition blocks? That seems to be the requirement.

```    listener.addListenerRule(
      `listener-rule-${i}-${pulumi.getStack()}`,
      {
        conditions: [
          {
            hostHeader: {
              values: [appHost],
            },
            pathPattern: {
              values: [pathPattern],
            },
          },
        ],
        actions: [
          {
            type: 'forward',
            targetGroupArn: targetGroup.arn,
          },
        ],
      }
    );```


You're probably right there. Two separate conditions

My bad. Thank you :slightly_smiling_face: