Status 403 on AWS Lambda
See original GitHub issueHi All,
I can deploy the terracotta on the AWS Lambda by following this tutorial :
https://terracotta-python.readthedocs.io/en/latest/tutorials/aws.html
I had no problem accessing its apidoc pages when it was deployed. However, when I try to put the address from the API (RGB) into my Leaflet page, it always gives me the “Forbidden” error message 403.
I believe it is not the terracotta problem but more to AWS settings. Do you have any suggestions on which tutorial I can follow/read to overcome these issues?
Thank you in advance for your time.
Best regards, Zufry M. I.
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Troubleshoot HTTP 403 errors from API Gateway - Amazon AWS
An HTTP 403 response code means that a client is forbidden from accessing a valid URL. The server understands the request, but it...
Read more >AWS Lambda function REST API end point - 403 error
Supposedly the Lambda is exposed through an AWS API Gateway. One reason why you'd get 403 on a fresh "no authentication" API Gateway...
Read more >AWS Lambda invocations intermittently fail with 403 ... - GitHub
A customer is experiencing intermittent 403 Forbidden failures in Virtual Services that delegate to AWS Lambda functions.
Read more >Resolve Amazon API Gateway HTTP 403 Forbidden error
This particular error code arises due to a number of reasons like “The caller isn't authorized to access an API that's using AWS...
Read more >Data action returns a 403 error - Genesys Cloud Resource ...
The AWS Lambda function that you are trying to invoke does not exist. · The policy in your AWS account does not grant...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed in #278. This one has been around way too long.
Yes, an ooold one #114… 😬