1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi,
You seem to be in a similar situation to https://stackoverflow.com/questions/76009085/the-api-with-id-xxx-doesn-t-include-a-route-with-path-having-an-integration
So, the solution for this question may also work for you.
Best.
Didier
Contenus pertinents
- demandé il y a 7 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
Thanks for the information. This error message turned out not to be the problem. The problem is because I didn't specify the identity source in my url so my lambda authorizer couldn't be invoked. Once I fixed this, and specify the identity source, wss://xxxxx.execute-api.us-east-2.amazonaws.com/demo?QueryString1=string1 my lambda authorizer could be invoked. And the error message "The API with ID xxxxxx doesn’t include a route with path /* having an integration arn:aws:lambda:us-east-2:xxxxxx:function:websocket-lambda_auth-new" is still there oddly, but everything is working fine now.