Hello:
You can provide the key as the result of a lambda authorizer which will have access to headers, url parameters and query string, but not body parameters.
https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-api-key-source.html
Regards,
Bob
Bob,
Thank you for taking time to reply.
I am the same person asking on this thread: https://forums.aws.amazon.com/thread.jspa?messageID=887871󘰿
I could have asked both my questions in one thread but they are not related so I created a thread for each of my question.
so based on this: https://forums.aws.amazon.com/thread.jspa?messageID=887871󘰿
I will be doing authorization in the Integration level... meaning I won't be having the Authorizer configured anymore
how am I going to enforce x-api-key without an authorizer?
Hello:
Unfortunately there isn't currently an option that would support your use case. Apologies for the inconvenience.
Regards,
Bob
Relevant content
- asked 6 months ago
- asked 9 months ago
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 9 months ago