Hi. I am using Pulumi with Localstack for testing my AWS deployment before I move into AWS. I am trying to create WAFv2 ACL rules and it looks like Pulumi is not hitting my Localstack endpoint but instead hitting AWS. I used this blog post for inspiration on how to set up Pulumi: https://delitescere.medium.com/pulumi-and-localstack-beyond-the-basics-d993f3b94d17 I have a YAML template that has the following (and gets merged to form a

Pulumi.yaml

.

config:
  aws:accessKey: test
  aws:secretKey: test
  aws:region: us-east-1
  aws:skipCredentialsValidation: true
  aws:skipRequestingAccountId: true
  aws:endpoints:
    - acm: ${LOCALSTACK_ENDPOINT}
      amplify: ${LOCALSTACK_ENDPOINT}
      apigateway: ${LOCALSTACK_ENDPOINT}
      ...
      waf: ${LOCALSTACK_ENDPOINT}

When Pulumi tries to create a WAFv2 ACL rule, I get an error back that is indicative of Pulumi trying to actually contact AWS and not Localstack. Is there a reference document somewhere from Pulumi (or on GitHub?) that can tell me what the service name keys should be for all of the AWS services; i.e. an enumeration of the keys for the

aws:endpoints

plugin YAML array object? Thank you very much.

Our README mentions "Custom Endpoints Guide" but does not link to it, perhaps https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/custom-service-endpoints can be of use

That's it! https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/custom-service-endpoints#available-endpoint-customizations mentions

wafv2

. Thank you very much.