1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Ok, problem solved, looks like the Resource for all methods doesn't work for WebSocket API case (used code example for HTTP case). After I changed to use event['methodArn'] or 'arn:aws:execute-api:us-east-1:{aws-account-id}:{api-id}/development/$connect', it works.
répondu il y a 7 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
The log from API GW is: "The client is not authorized to perform this operation."
BTW, I saw this error from the Lambda authorizer's trigger which is the API WebSocket API in the AWS console: "The API with ID 7rypk365yl doesn’t include a route with path /* having an integration arn:aws:lambda:us-east-1:370783930566:function:apigwLambdaAuthorizer."
For WebSocket API, I only need config the Lambda authorizer for the connect route?
Thank you!