Menu
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 {"message":"Forbidden"} (same message if I connect it to the actual lambda service).
Any advice on how to make it accessible?
453
The HTTP 403 Forbidden error most commonly occurs when private DNS is enabled for an API Gateway interface VPC endpoint that's associated with a VPC. In this scenario, all requests from the VPC to API Gateway APIs resolve to that interface VPC endpoint.
Clear Your Browser Cookies and Cache Clearing the cache won't affect your browsing experience much, but some websites may take a couple of extra seconds to load as they re-download all the previously cached data. Clearing cookies means you'll have to sign in again to most websites.
The 403 Forbidden error appears when your server denies you permission to access a page on your site. This is mainly caused by a faulty security plugin, a corrupt . htaccess file, or incorrect file permissions on your server.
If you set 'API Key Required' option to true, please check below.
113
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
