1 回答
- 最新
- 投票最多
- 评论最多
1
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?
已回答 2 年前
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
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!!