Created Lambda Hello world function using Node.js and created API GateWay trigger for Get call, tried the URL to access Lambda function,  getting below error.

message: &quot;Internal server error&quot;.

(very new to AWS)


message: &quot;Internal server error&quot; when try to access aws gateway api

In this question https://stackoverflow.com/questions/31329958/how-to-pass-a-querystring-or-route-parameter-to-aws-lambda-from-amazon-api-gatew

shows how to map query string params to AWS lambda using API gateway. I would like to do the same but mapping POST values instead of query-string. I tried:

    {
        &quot;values&quot;: &quot;$input.params()&quot;
    }

but did not work, I don&#39;t see the actual form data. BTW I am posting using: 

`application/x-www-form-urlencoded`

I get my response from my lambda function, so I know it is invoking lambda fine, but my problem is that I don&#39;t see the POST params anywhere. I can;t figure out how to map them. I dump all I get on Lambda side and here it is:

     {&quot;values&quot;:&quot;{path={}, querystring={}, header={Accept=*/*, Accept-Encoding=gzip, deflate, Accept-Language=en-US,en;q=0.8, Cache-Control=no-cache, CloudFront-Forwarded-Proto=https, CloudFront-Is-Desktop-Viewer=true, CloudFront-Is-Mobile-Viewer=false, CloudFront-Is-SmartTV-Viewer=false, CloudFront-Is-Tablet-Viewer=false, CloudFront-Viewer-Country=US, Content-Type=application/x-www-form-urlencoded, Origin=chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop, Postman-Token=7ba28698-8753-fcb1-1f48-66750ce12ade, Via=1.1 6ba5553fa41dafcdc0e74d152f3a7a75.cloudfront.net (CloudFront), X-Amz-Cf-Id=sc8C7dLcW0BHYopztNYrnddC0hXyFdBzHv0O9aWU1gKhd1D_J2HF3w==, X-Forwarded-For=50.196.93.57, 54.239.140.62, X-Forwarded-Port=443, X-Forwarded-Proto=https}}&quot;}

How to pass a params from POST to AWS Lambda from Amazon API Gateway

In order to prevent users who have not logged in to call my lambda function through the AWS API Gateway, I&#39;m using the Custom Authorizer lambda solution.

If the request is authorized (200) and I get a response from the called lambda everything works fine and I get the `Access-Control-Allow-Origin` header.

But if the request is not authorized, I get a 401 that has no `Access-Control-Allow-Origin` header, therefore preventing me from reading the 401 status of the response and redirecting the user to the log-in page.

I believe this is because the Custom Autorization mechanism is unaware that the request needs to use CORS. Does anyone know that this is actually the issue? Are you aware of any possible solution?

401 return from an API Gateway Custom Authorizer is missing &#39;Access-Control-Allow-Origin&#39; header

The stage name is added to the url when I deploy the API. Let&#39;s say the stage name is &quot;test&quot;, then the generated URL for the resource includes the stage name. Something like:
https://abcabc.execute-api.us-east-1.amazonaws.com/test/my/path

I would like to remove the stage name in the URL. How can I do it?

AWS API Gateway - Remove Stage Name From URI

When I run CloudFormation `deploy` using a template with API Gateway resources, the first time I run it, it creates and deploys to stages. The subsequent times I run it, it updates the resources but doesn&#39;t deploy to stages.

Is that behaviour as intended?  If yes, how&#39;d I get it to deploy to stages whenever it updates?

(Terraform mentions a similar issue: https://github.com/hashicorp/terraform/issues/6613)


CloudFormation doesn&#39;t deploy to API gateway stages on update

I am trying a small example  with AWS API Gateway and IAM authorization. The AWS API Gateway generated the below Endpoint : 

    https://xyz1234.execute-api.us-east-2.amazonaws.com/Users/users
with POST action and no parameters.

Initially I had turned off the IAM for this POST Method and I verified results using Postman it works. 
Then I created a new IAM User and attached AmazonAPIGatewayInvokeFullAccess Policy to the user thereby giving permission to invoke any API&#39;s. Enabled the IAM for the POST Method.

I  then went to Postman - and added Authorization with AccessKey, Secret Key, AWS Region as `us-east-2` and Service Name as `execute-api` and tried to execute the Request but I got InvalidSignatureException Error with 403 as return code. 

The body contains following message :

    Signature expired: 20170517T062414Z is now earlier than 20170517T062840Z (20170517T063340Z - 5 min.)&quot; 

What am I missing ?

Signature expired: is now earlier than error : InvalidSignatureException

There are similar questions but they have answers that I have tried.
I&#39;m not sure what I could be doing wrong but any help would appreciated.

Test details:
[![enter image description here][1]][1]

The Error from a method-execution test; PUT request:

    Execution log for request test-request
    Mon Oct 16 10:13:47 UTC 2017 : Starting execution for request: test-invoke-request
    Mon Oct 16 10:13:47 UTC 2017 : HTTP Method: PUT, Resource Path: /pop-data-xmlz/test.xml
    Mon Oct 16 10:13:47 UTC 2017 : Method request path: {item=test.xml, folder=pop-data-xmlz}
    Mon Oct 16 10:13:47 UTC 2017 : Method request query string: {}
    Mon Oct 16 10:13:47 UTC 2017 : Method request headers: {Content-Type=application/xml}
    Mon Oct 16 10:13:47 UTC 2017 : Method request body before transformations: &lt;test&gt;
    test string
    &lt;/test&gt;
    Mon Oct 16 10:13:47 UTC 2017 : Request validation succeeded for content type application/json
    Mon Oct 16 10:13:47 UTC 2017 : Execution failed due to configuration error: API Gateway does not have permission to assume the provided role
    Mon Oct 16 10:13:47 UTC 2017 : Method completed with status: 500

I am following the API Gateway To S3 tutorial (http://docs.aws.amazon.com/apigateway/latest/developerguide/integrating-api-with-aws-services-s3.html) and attempting to execute a PUT request.

The API Gateway is in us-east-1 and the S3 bucket in us-east-2.



The created Role: **APIGatewayProxyCustom**

A policy (pop-date-ingest) is attached that allows PUT request to S3 buckets.
[![enter image description here][2]][2]

The Role has a trust relationship set:
[![enter image description here][3]][3]


  [1]: https://i.stack.imgur.com/MtkuV.png
  [2]: https://i.stack.imgur.com/Rygj7.png
  [3]: https://i.stack.imgur.com/7lZST.png

AWS API Gateway error: API Gateway does not have permission to assume the provided role as S3 proxy

I have a Lambda function that has an exposed API Gateway endpoint, and I can get the URL for that via the AWS console. However, I would like to get that URL via API call. Neither the [Lambda API documentation][1] nor the [API Gateway documentation][2] seem to have that information (or perhaps I&#39;ve missed it), so is this even possible in the first place?


  [1]: http://docs.aws.amazon.com/lambda/latest/dg/API_Operations.html
  [2]: http://docs.aws.amazon.com/apigateway/api-reference/resource/api-gateway/

How do I find the API endpoint of a lambda function?

I&#39;m working with AWS API Gateway and AWS Lambda. Often I face this type of error message when attempt to deploy API. The error message says to select a deployment stage. But I still selecting and trying to deploy! but same error occur!

[![Screenshot of pop up error message][1]][1]

In this API I have multiple resources with multiple methods. Previously I succeed to deploy this same API with the same way. But now I can&#39;t deploy it.

Please anyone help me to fix it. For addition: I don&#39;t use AWS CLI tool, just use AWS web dashboard.

  [1]: https://i.stack.imgur.com/OAmZd.png

No integration defined for method - Choose a stage where your API will be deployed

I see in the [API Gateway FAQ][1] that it is possible to access the request headers sent to the API Gateway...

&gt; If you already utilize OAuth tokens or any other authorization
&gt; mechanism, you can easily setup API Gateway not to require signed API
&gt; calls and simply forward the token headers to your backend for
&gt; verification.

However, I can find no example of how to do so in the documentation and it is unclear how to access this data using Lambda.

I am able to set up an open API and gain access to the JSON object that is part of a POST ([Walkthrough: API Gateway and Lambda Functions][2]), but in order to implement a OAuth 2.0 style API with my own provider I need access to the &quot;Authorization&quot; header.

My preference is to set this up using Lambda and Java 8, but an example using node.js would also be helpful in understanding how to accomplish this.


  [1]: https://aws.amazon.com/api-gateway/faqs/
  [2]: https://docs.aws.amazon.com/apigateway/latest/developerguide/getting-started.html

How to access HTTP headers for request to AWS API Gateway using Lambda?

What do you think are the Pros and Cons of using Lambda integration with and without the proxy feature in AWS API Gateway (and more specifically, when using the Serverless framework)? Here&#39;s what I think up to now:

**Lambda Integration with Proxy**

 - **Pro**: One can rapidly prototype and code without worrying about all the needed configuration details (and reinventing a few wheels like generic template mappings, etc).
 - **Pro**: It&#39;s really easy to return any status code and custom headers, while at the same time there&#39;s a generic way to read the body, headers, parameters, of the request.
 - **Con**: Everything is done in code, so autogenerating documentation is a bit more difficult. Dependencies (headers, models, returned status codes) are &quot;hidden&quot; in the code.

**Lambda Integration without Proxy**

 - **Con**: Involves *a lot* more of work to set it up, and this configuration might be duplicated in different resources.
 - **Pro**: It allows one to decouple what the lambda receives and returns, and how it gets mapped to different HTTP status codes, headers, and payloads.
 - **Pro**: Very useful because it stipulates upfront what it returns, and what it requires in terms of headers and payloads.
 - **Pro**: The hard work when setting up everything is useful in the long run because one can export everything to Swagger, so others can use this to generate different SDKs for it.

What are your thoughts? Do you generally use Lambda Proxy or plain Lambda integrations? What do you prefer, and why?

**EDIT**: So far, I&#39;m inclined to always choose not to use the proxy features due to the reasons mentioned (decoupling and stating dependencies -headers, status codes, etc- upfront).

Lambda Integration vs. Lambda Proxy: Pros and Cons

I am trying to call a Lambda Function through AWS API Gateway. 
When I mention Authentication type NONE it works fine but API become public and anyone with url can access my API.
To make API call secure, I am using Authentication type AWS_IAM and 
also attached AmazonAPIGatewayInvokeFullAccess policy to my user but getting this error:

    { message: &quot;Missing Authentication Token&quot;}

I don&#39;t know what I am missing here.

Missing Authentication Token while accessing API Gateway?

In order to deal with the microservice architecture, it&#39;s often used alongside a Reverse Proxy (such as nginx or apache httpd) and for cross cutting concerns implementation  [API gateway pattern is used][2]. Sometimes Reverse proxy does the work of API gateway.

It will be good to see clear differences between these two approaches.
It looks like the potential benefit of API gateway usage is invoking multiple microservices and aggregating the results. All other [responsibilities][1] of API gateway can be implemented using Reverse Proxy. Such as:

 - Authentication (It can be done using nginx LUA scripts);
 - Transport security. It itself Reverse Proxy task;
 - Load balancing
 - ...

So based on this there are several questions:

 1. Does it make sense to use API gateway and Reverse proxy simultaneously (as example request -&gt; API gateway -&gt; reverse proxy(nginx) -&gt; concrete microservice)? In what cases ?
 2. What are the other differences that can be implemented using API gateway and can&#39;t be implemented by Reverse proxy and vice versa?

  [1]: https://auth0.com/blog/2015/09/13/an-introduction-to-microservices-part-2-API-gateway/
  [2]: https://www.nginx.com/blog/building-microservices-using-an-api-gateway/

API gateway vs. reverse proxy

Although CORS has been set up through API Gateway and the `Access-Control-Allow-Origin` header is set, I still receive the following error when attempting to call the API from AJAX within Chrome:

&gt; XMLHttpRequest cannot load http://XXXXX.execute-api.us-west-2.amazonaws.com/beta/YYYYY. No &#39;Access-Control-Allow-Origin&#39; header is present on the requested resource. Origin &#39;null&#39; is therefore not allowed access. The response had HTTP status code 403.


I attempted to GET the URL through [Postman](https://www.getpostman.com/) and it shows the above header is successfully passed:

[![Passed headers][1]][1]


And from the OPTIONS reponse:

[![Response headers][2]][2]


How can I call my API from the browser without reverting to JSON-P?


  [1]: http://i.stack.imgur.com/cowzz.png
  [2]: http://i.stack.imgur.com/xRCeH.png

API Gateway CORS: no &#39;Access-Control-Allow-Origin&#39; header

I am trying to set up a hello world example with AWS lambda and serving it through api gateway. I clicked the &quot;Create a Lambda Function&quot;, which set up the api gatway and selected the Blank Function option. I added the lambda function found on [AWS gateway getting started guide][1]:  

    exports.handler = function(event, context, callback) {
      callback(null, {&quot;Hello&quot;:&quot;World&quot;});  // SUCCESS with message
    };
The issue is that when I make a GET request to it, it&#39;s returning back a 502 response `{ &quot;message&quot;: &quot;Internal server error&quot; }`. And the logs say &quot;Execution failed due to configuration error: Malformed Lambda proxy response&quot;.

  [1]: http://docs.aws.amazon.com/apigateway/latest/developerguide/getting-started.html#getting-started-new-lambda

AWS lambda api gateway error &quot;Malformed Lambda proxy response&quot;

I&#39;m currently using NodeJS to build a bot on AWS lambda via AWS Api Gateway and I&#39;m running into an issue with POST requests and JSON data. My api uses &#39;Use Lambda Proxy integration&#39; and even when I test the proxy sending a content-type of Application/json and some json in the body e.g `{&quot;foo&quot;:&quot;bar&quot;}` I can&#39;t access the object without parsing it first

e.g

      var json = JSON.parse(event.body);
      console.log(json.foo);

Now I know this doesn&#39;t seem a big deal just running it through JSON.parse, but I&#39;ve seen a number of other examples where this isn&#39;t the case at all. see here https://github.com/pinzler/fb-messenger-bot-aws-lambda/blob/master/index.js

Do I need to add anything to my API gateway to handle this correctly? my &#39;request body&#39; step in the &#39;post method request&#39; section has a content-type of application/json set-up for the request body. 

The readme for the example above doesn&#39;t seem to use proxy integration as far as I can tell so I&#39;m not sure what I should be doing here

Getting json body in aws Lambda via API gateway

For instance if I want to return a specific 400 error for invalid parameters or perhaps a 201 when the lambda function call resulted in a create.

I&#39;d like to have different http status codes but it looks like api gateway always returns a 200 status code even if the lambda function is returning an error.

Is there a way to change the http status codes returned by Amazon API Gateway?

I am trying to create a lambda service on AWS and have it accessed from outside via the API gateway with no authentication or restriction required.

To make things easy I set the gateway for now to be a Mock.

On the Get method of the API, the Authorization is set to `None` and the API Key is `not required`.

When I try this, I get `{&quot;message&quot;:&quot;Forbidden&quot;}`
(same message if I connect it to the actual lambda service). 

Any advice on how to make it accessible?


getting message: forbidden reply from AWS API gateway

This does not make sense to me at all. When you create a new API Gateway you can specify whether it should be regional or edge-optimized. But then again, when you are creating a custom domain name for API Gateway, you can choose between the two.

Worst of all, you can mix and match them!!! You can have a regional custom domain name for an edge-optimized API gateway and it&#39;s absolutely meaningless to me!

Why these two can be regional/edge-optimized separately? And when do I want each of them to be regional/edge-optimized?

Regional/Edge-optimized API Gateway VS Regional/Edge-optimized custom domain name

I have created an API Key and added it to my functions. I have then deployed the api and tested it but still get:

    &quot;message&quot;: &quot;Forbidden&quot;

How do I pass the api key with my JSON request as I have been using &quot;x-api-key&quot;: &quot;theKey&quot;?

Using an API key in Amazon API Gateway

for instance if we want to use 

`GET /user?name=bob `

or

`GET /user/bob`

How would you pass both of these examples as a parameter to the Lambda function?

I saw something about setting a &quot;mapped from&quot; in the documentation, but I can&#39;t find that setting in the API Gateway console.

- `method.request.path.parameter-name` for a path parameter named `parameter-name` as defined in the Method Request page.
- `method.request.querystring.parameter-name` for a query string parameter named `parameter-name` as defined in the Method Request page.

I don&#39;t see either of these options even though I defined a query string.


How to pass a querystring or route parameter to AWS Lambda from Amazon API Gateway

I have 2 Lambda functions - one that produces a quote and one that turns a quote into an order.
I&#39;d like the Order lambda function to call the Quote function to regenerate the quote, rather than just receive it from an untrusted client.

I&#39;ve looked everywhere I can think of - but can&#39;t see how I&#39;d go about chaining or calling the functions...surely this exists!

Can an AWS Lambda function call another

I have an AWS api that proxies lamba functions. I currently use different endpoints with separate lambda functions:

    api.com/getData --&gt; getData
    api.com/addData --&gt; addData
    api.com/signUp --&gt; signUp

The process to manage all the endpoints and functions becomes cumbersome. Is there any disadvantage when I use a single endpoint to one lambda function which decides what to do based on the query string?

    api.com/exec&amp;func=getData --&gt; exec --&gt; if(params.func === &#39;getData&#39;) { ... }

aws api gateway &amp; lambda: multiple endpoint/functions vs single endpoint

I&#39;m currently writing a Node.js lambda function, in which I want to log the incoming requester&#39;s public IP address. I&#39;ve been looking through both the API Gateway and Lambda docs all day, but haven&#39;t found a solution.

Does the lambda `event` object include request metadata I can use to extract the user&#39;s IP?

How can I retrieve a user&#39;s public IP address via Amazon API Gateway + Lambda (node)

I have some issue with API gateway. I made a few API methods, sometimes they work longer than 10 seconds and Amazon returns 504 error. Here is screenshot below: 

[![enter image description here][1]][1]

Please help! How can I increase timeout?

Thanks!


  [1]: http://i.stack.imgur.com/5v0CV.png

All Aws Api-Gateway Solutions on Gang of Coders

Total of 25 Aws Api-Gateway Solutions

message: "Internal server error" when try to access aws gateway api