AWS API Gateway will not open

Question

I created the lambda function "hello world" and then deployed it to the endpoint using the AWS API gateway :

All the settings are very simple, but I was sure that you would change the security to “open”, and while I was told that it could take 15 minutes to resolve the domain, I found that even after 30 I received the following response from the “open” final points:

{"message":"Missing Authentication Token"} 

Am I missing something obvious? Wasn't it accessible with what I did?

---

Please note that it was pointed out that this image has a PUT, not a GET. I tried both and both returned to errors. Just to verify that I ran GET and PUT through Postman and got a similar but not identical answer:

and then get ...

When I test the lambda function in the console, it starts successfully, but runs it in the Gateway API, this gives me another junction of the same error:

Tue Sep 29 20:57:43 UTC 2015: Execution failed due to a configuration error: Invalid permissions for lambda function

and yet I used the default permissions offered by the console. The lambda function itself is very simple and is located here: code

Answer 1

I had the same problem with the deployed API, which often hit at noon when the requests stopped working and failed with the {Missing Authentication Token} error

My problem was not the URL or the stage that was not deployed, but I know AWS throws this error for both reasons.

However, I found a command to invalidate the apigateway cache, because in my case I used my own domain attached to the cloud.

 aws apigateway flush-stage-cache --rest-api-id 97y41psdkg --stage-name dev 

After that, I stopped receiving {Missing Authentication Token}

Answer 2

Today I had a certain problem. All that I did did not work, but in the end it turned out. in order for the changes to take effect, you need to install the API.

So, first go to Resources and click the Deploy API button. He will ask for the deployment phase. After deployment, I could call my API without any problems.

I know that some time has passed since you posted this question, but I thought it might come in handy for other people.

Answer 3

You need to use the "AWS Signature" on the "Authorization" tab in Postman. See the AWS Guide for what to enter in these fields:

http://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-use-postman-to-call-api.html

Answer 4

Please use the resource name at the end of the api url.

https: //***********.execute-api.us-east-1.amazonaws.com/Stag/number

Here the number is my resource name