If you click into it, you’ll see a 200 response. Now, we’re going to select the Method Response (highlighted in red, above). Integration Response: This is what we believe will be coming back from the integration (grayed out here, as mentioned, we don’t have access to it with the proxy integration).Method Response: This is similar to the Method Request, where you can define what the method can return.Integration Request: This is what the API is integrating with to, well, create the API! It’s how the gateway communicates with Lambda.This includes auth, input body, headers, and query string params. The Method Request: This is the part of your API exposed to your users.Now we’re coming to a screen that will look a little complex, but no worries, you’ll soon know you’re way around here pretty well! However, as you start to use it more, you might want to not check this as you so that you can retain the ability to configure an Integration Response (disabled for the proxy integration). It will even auto-fill the function as you start typing, as you can see below. I use the default location for me which is us-east-2, but yours may be different and that’s fine.įor simplicity’s sake, I’m going to check the box for ‘Use Lambda Proxy Integration’, which is a pretty quick and easy way to bring in your function. We’ll select this option along with a few others. This will take you to a screen to connect your API to a Lambda. Now in that same “Actions” dropdown, you can select “Create Methods” and then “GET” and click the checkmark that will create it. Don’t forget to ‘Enable API Gateway CORS’ as well and then click “Create Resource”. Fill the ‘resource name’ with a name (the path will auto-generate). Then, in the Action dropdown, we’ll select “Create Resource”-a pane will come up titled “New Child Resource”. In the next screen select REST API and select ‘Build’.
Search for API Gateway, click Create API.
0 kommentar(er)
