Skip to content Skip to sidebar Skip to footer

Api Gateway Custom Domain Forbidden

Api Gateway Custom Domain Forbidden. I created a hello world. I went to aws lambda in aws console.

amazon web services Receving 403 forbidden from Custom Domain in AWS
amazon web services Receving 403 forbidden from Custom Domain in AWS from stackoverflow.com

Select +add, or select an existing endpoint that you want to update. After a custom domain name is created in api gateway, you must create or update your dns provider's resource record to map to your api endpoint. In the left navigation, select custom domains.

In The Window On The Right, Select The Type Of Endpoint For.


Without such a mapping, api requests. We are using serverless pro to deploy our api. Select +add, or select an existing endpoint that you want to update.

I Went To Aws Lambda In Aws Console.


When we are calling api with custom domain it is throwing 403 forbidden. So, the problem is that the request fails with a 403 forbidden error, because api gateway is unable to set the correct host header, which is required for the request to succeed. These troubleshooting steps will come in handy to identify the cause of the error:

After A Custom Domain Name Is Created In Api Gateway, You Must Create Or Update Your Dns Provider's Resource Record To Map To Your Api Endpoint.


Without such a mapping, api requests. I created a hello world. In the left navigation, select custom domains.

We Have Added A Custom Domain To The Api Gateway.


After a custom domain name is created in api gateway, you must create or update your dns provider's resource record to map to your api endpoint. I setup everything and the response i get back is missing authentication token.

Post a Comment for "Api Gateway Custom Domain Forbidden"