Receving 403 forbidden from Custom Domain in AWS Api Gateway

Question

I'm trying to build a serverless app with AWS. My API is working fine, but my custom domain is not. I'm receiving a 403 forbidden answer. This is how it's configured my custom domain:

And then I'm using the Target URL provided by this Custom Domain in Route 53 as CNAME. How can I fix this?

Does it work if you use the API Gateway endpoint directly (i.e. bypassing the custom domain)? If not, it could be an issue with the API Gateway -> Lambda permissions. — Tom, Oct 07 '18 at 17:31
The API gateway endpoint works, what doesn't work is the target domain offered by custom domain, neither the domain used in Route 53 with CNAME — Filipe Ferminiano, Oct 07 '18 at 17:41
And your CNAME is pointing to the `*.cloudfront.net` domain, not the `*.execute-api.[region].amazonaws.com` one? — Tom, Oct 07 '18 at 17:57
The CNAME is pointing to *.execute-api.us-west-2.amazonaws.com which is the one that custom domain gaves me. How can I get the cloudfront domain? — Filipe Ferminiano, Oct 07 '18 at 18:03
If you go to API Gateway -> Custom Domain Names, there should be a CloudFront domain listed under "Target Domain Name". — Tom, Oct 07 '18 at 18:06
I updated to clodfront url, let's wait for some time to check it works — Filipe Ferminiano, Oct 07 '18 at 18:28
It's working now. @Tom can you submit an answer so I accept it? — Filipe Ferminiano, Oct 07 '18 at 19:02

score 4 · Accepted Answer · answered Oct 07 '18 at 19:12

4

The CNAME should point to the CloudFront endpoint (*.cloudfront.net) rather than the API Gateway endpoint (*.execute-api.[region].amazonaws.com).

The CloudFront endpoint can be found by going to API Gateway -> Custom Domain Names. A CloudFront domain should be listed under "Target Domain Name".

answered Oct 07 '18 at 19:12

Tom

1,660
8
16

9

That is the case for _Edge Optimized_ endpoints. I'm wondering if there is a way to set up this with _Regional_ ones (*.execute-api.[region].amazonaws.com). – Dmitry Kolomiets Mar 20 '19 at 06:37
I'm also facing same issue but i don't see any Target domain name. I'm having regional endpoint. – uni Dec 15 '21 at 12:06

Receving 403 forbidden from Custom Domain in AWS Api Gateway

1 Answers1