By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Websocket API connect failed to revoke lambda authorizer

0

I created a lambda function to authorize an API connect. No matter what I tried, the lambda function can't be involved. In the configuration-->triggers of lambda function, I noticed the following:

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.

Any insights? Thanks

Topics
ServerlessComputeFront-End Web & MobileNetworking & Content Delivery
Tags
ServerlessAWS LambdaAmazon API Gateway
Language
English
AWS new developer
asked 9 months ago513 views
1 Answer
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

profile pictureAWS
EXPERT
Didier_Durand
answered 9 months ago
  • AWS new developer
    9 months ago

    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.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content