Cannot Create Lambda Authorizer Using API Gateway WebSocket Console, Error: Unexpected Key 'ProviderArns' Found in Params
I cannot add a lambda authorizer to my WebSocket API from the AWS Console.
When I click the Create button, I get a red error banner at the top with the text: Unexpected key 'ProviderArns' found in params and nothing happens.
I've even tried creating a blank test WebSocket API and a blank test Lambda function, but I still get this error when creating a a new authorizer. I have tried every combination of having or not having Lambda Invoke Roles or Identity Sources, but I still get this error.
This was all working yesterday, but my authorizers spontaneously stopped working today, and I haven't been able to add/edit them. I have since added a CloudWatch log role for logging, but even when I remove this, all my webSockets are still broken.
The authorizers in my REST APIs are still working just fine and I can add/delete/edit these authorizers with no problem.
Does anyone know what's going on or at least how to fix/circumvent it?
- Newest
- Most votes
- Most comments
Are you able to use AWS CLI to create an authorizer to work around the issue?
aws apigatewayv2 create-authorizer --name my-ws-authorizer --api-id <api id> --authorizer-type REQUEST --identity-source route.request.header.Auth --authorizer-uri arn:aws:apigateway:<region>:lambda:path/2015-03-31/functions/arn:aws:lambda:<region>:<accountid>:function:<function name>/invocations
I was unable to reproduce the issue on my end in the us-east-1 region. However, if you constantly receive the error, can you capture a HAR file to see what error you see?
Relevant content
- asked 6 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Using the CLI worked. After doing that, the console is working now too... must've been some weird bug. Thank you so much for the help!!