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

The key is provided in the API request, not in the route configuration. There's a trivial example here (bullet 4): <https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-how-to-call-websocket-api-wscat.html>

To configure which key is used, there is the `routeKey` arg, which is mandatory, so presumably you're already providing that?

<https://www.pulumi.com/registry/packages/aws/api-docs/apigatewayv2/route/#routekey_nodejs>

i am not referring to routing keys, but the header "X-API-Key'"

Ah. Afaik, apiKeyRequired controls routing keys, not headers...

image.png

the docs refer to the normal api-key header i mentioned above being the default place to get the key from the request

Then I'm afraid we've gone beyond my knowledge :disappointed:

figured it out, had to use  awsx.apigateway.createAssociatedAPIKeys