2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hi,
The API Gateway APIs can return "Missing Authentication Token" error for multiple reasons, so I recommend that you take a look at the following Knowledge Center post to identify what's causing the error, and apply the most appropriate solution.
If none of the recommended actions solve your problem, I suggest you add more information so that we can help you to find the cause.
0
Sometimes I noticed this can be just to to the fact that stages do not get deployed, thus make sure your api gw stage is indeed deployed
I can confirm it's definitely deployed!
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
Hi Mikel, I appreciate the assistance! I have already followed the knowledge center post to the best of my ability. I've verified I'm sending a json to the correct resource. As far as I know, I've turned off all Authorisation on the API and LAMBDA function. I also haven't modified any gateway response. I've added the resource policy to allow everything ("Resource": "arn:aws:execute-api:us-east-1:326280663162:5mkjwr5c31/api//").
It's interesting. If I send my request via cmd curl on the {url}/api/api it says it couldn't resolve application.
Is there any particular information I should provide? I wish I could provide screenshots or speak directly with someone!
Hi,
Assuming that are using a REST API, with a Regional API endpoint, that has been correctly deployed and that there is no authentication method configured... Could you check that the Method, URL and the path you are calling is indeed correct? https://{restapi-id}.execute-api.{region}.amazonaws.com/{stageName}/{resource}.