7
votes

I have created one API in AWS API Gateway. In that API I created one proxy resource with custom http endpoint. But when I access the API Gateway endpoint https://2r3g3ttr6y.execute-api.eu-east-1.amazonaws.com/production/abc/abc.html it is not working whereas the original HTTP endpoint is working perfectly fine.

I get {"message":"Forbidden"} response. Here is the setting:

enter image description here

NOTE: The above API Endpoint is just a dummy endpoint.

1
Are you sure this is an issue with the gateway and not whatever it is tied to? I had a lambda function behind a gateway that was returning a forbidden message because of errors with being invoked. It was very misleading.Brandon Miller
@BrandonMiller, I am damn sure this issue is not related to custom http end point as it is working perfectly fineuser3847894
I once again double checked. It is not the issue of http endpoint but API gatewayuser3847894
Maybe you applied a resource policy to your API? According to the Resource Policy page, under APIs > YourApi, If the Principal is set to AWS: ..., then authorization will fail for all resources not secured with AWS_IAM auth, including unsecured resources.Razvan
Make sure that stage IS deployediMysak

1 Answers

1
votes

This thing happened to me in the past because I forget to deploy my API.

Here how I fixed it:

Click Actions dropdown on the top -> Deploy API -> choose [New Stage] -> enter whatever name you want -> Deploy