Connecting Lambda to API Gateway (Getting started with AWS Lambda, part 3)

In this video I'll show you how to connect your Lambda function to API Gateway.

Watch the next video (Passing information through API Gateway):

► About Lambda
AWS Lambda is a compute service where you can upload your code to AWS Lambda and the service can run the code on your behalf using AWS infrastructure.

► Building an anagram solver with Lambda
Check out how I builded an anagram solver with Lambda, API Gateway, DynamoDB, S3 and CloudFront:

► Meal planning with Lambda and Trello
Check out how my girlfriend and I use Lambda and Trello as a weekly meal planner:

► About me

[chrisedwards]

I can't tell you how useful it is that you included the "Missing Authentication Token" error in your guide, because that's the error that I (and probably everyone else) run into. Amazon's own instructions don't help to avoid that error, because the interface has changed significantly since they made their guide.

[daviddaytona]

Thank you for providing such clear and well considered demonstrations on Lambda and associated services. Brilliant!

[SudipBhakta]

Save me a lot of time and money. I had previously deployed my HTTP server in an EC2 instance. Thanks a lot.

[sailorcto]

Any chance you could update this videos series? Many of the AWS consoles and interfaces have changed, so these instructional videos become stale. Thanks for putting them out in a very easy way to learn. Well done.

[PhillipBlanton]

If you're using Node.js version 6.x and getting the internal server error, then you need to modify the callback as follows...

callback(null, { statusCode: 400, body: });

It'll wrap your output in json during the [test] but the trigger will work as in the video.

[sam.kendrick]

Thank you so much for your time and effort! These are excellent videos.

[rajan]

When i tried to add triggers to my lamda function the api created is with method ANY by default and there are no options to choose Method type while create the trigger. On clicking the URL it says {message: "internal server error"}.

[vladyslavbabak]

Thanks, the 2nd method with using API gateway console was only working to me. AWS interface is a little bit different now... but it works.

[weiak]

Great tutorial, a light year better than the official one.

[pakpoomtivarkornkit]

Thanks! AWS Lambda is so much faster than Firebase Cloud Functions

[nyamurray]

Great video series, well presented, good examples.

[carolelachance]

Thank you for this interesting video. Do you have an example of managing POST request with NodeJS in Lambda ? Thanks

[shamilJaey]

Great set of tutorials. In a future video will it be possible for you to show us on how to protect Lambda functions and also the API methods (from API Gateway) ?

It would also be nice If you could do a series on Amazon Cognito and Amazon Dynamo DB

[sandeepkamboj]

I am getting "Internal server error" while using api. Can u suggest the solution.

[rodrigoruiz]

Your tutorials are great! Any chance you also have one teaching how to create a secure API with "Open with access key"?

[djjfresco]

Could you use Route53 to create a more friendly uri for your lambda function? Not sure if you've covered this - I haven't seen all your videos on this topic yet, but this series has been really helpful. thanks!

[meetzaveri]

What's purpose of integration request and response? What does it do while connecting to AWS lambda

[bigmacdoubleyouv]

My "Resource Name" and "Method" boxes do not pop up when I set a trigger. Also, at this point, the hello world is only for Node 6.10, which I am unsure if this makes a difference or if setting up the API Gateway Trigger has changed since the creation of this video. Please advise about the Resource Name and Method please.

[morikuldip]

in this video 0.34 minit you go lambda function but it first explain how to crate lambda function after understand next step if you any video for this topic then plz give me link

[Marcio_MN]

"Server Internal Error" (RESOLVED - But why!??):
If I connect the lambda function with the API through the lambda I got the "internal server error" which was solved by making the callback as indicated by Phillip...

callback(null, { statusCode: 200, body: });

However, if I connect them through the API Gateway as explained later on the video, I have to use the original's video callback or else it returns {"statusCode":200, "body":"8"}

Any ideia why? Clearly, there's a small difference on both connecting methods which I would like to understand. It's like one expects a plan body response and the other expects a header status code and body in json format but I don't know why since the request headers of both URLs are exaclty the same