api gateway regional custom domain is not working

Question

I'm testing to make mobile game server with AWS's Lambda and API gateway. At the API gateway, I try to make custom domain using 2 types endpoint, regional a.domain.com and edge optimized b.domain.com. The edge optimized endpoint is fine, it works.

But the regional endpoint is not working. it returns ERR_CONNECTION_REFUSED. the regional endpoint url can't submit to record set using aws console.

So I'm using aws-cli for editing record set in the route53.

Without knowledge of the specific domain name you"re working on and the assigned endpoint hostname that it should be pointing to, it isn't really possible to diagnose this... although the error suggests a DNS misconfiguration, since there is nothing you could do in API Gateway itself that would cause Err Connection Refused -- that implies you're somehow connecting to a system that is online but doesn't actually have a web server running... and this not a condition that you could cause either accidentally or deliberately, with API Gateway. — Michael - sqlbot, Jan 18 '18 at 01:37
I have a similar issue but get a 403 {"message":"Forbidden"}. I'm guessing that means my custom domain is actually resolving - so could be a different issue. My REST APIs work, but my HTTP one refuses to. — square_eyes, Aug 13 '20 at 06:07
@square_eyes were you able to resolve forbidden error for custom domain? — uni, Dec 15 '21 at 11:37

score 36 · Answer 1 · answered Nov 03 '19 at 19:13

36

I had the same issue.

It appears that when using API Gateway with regional custom domains only HTTPS is supported and API Gateway does not redirect from HTTP to HTTPS.

So just use https://a.domain.com

answered Nov 03 '19 at 19:13

RomanHotsiy

4,978
1
25
36

O boy you saved my life. For 2 days in a row was looking for an answer... – Teodor Scorpan Jul 23 '20 at 10:09
Facepalm... thanks for your answer, wish I found it sooner – oortCloud Dec 06 '20 at 08:41
1

This is a life saver, I was looked at every answer on stackoverflow to find that this was the problem. Thanks alot! – Fahd Lyousfi Feb 17 '21 at 23:57
I have never sworn so much trying to fix this problem. Thanks! – jonface Mar 11 '21 at 21:11
I tried your way now its giving "message": "Forbidden" , do you have idea on this? – uni Dec 15 '21 at 11:38
still relevant and helpful! nowhere in the AWS docs is this clearly called out as a warning – Jeremiah Shore Apr 29 '22 at 22:40
oh my goodness. So stupid, but thank you so much! – A Simple Programmer Mar 02 '23 at 18:00

score 0 · Answer 2 · answered Jun 28 '22 at 18:14

If you are still getting the 403 {"message":"Forbidden"} response it's because you are probably trying to call the endpoint from the API Gateway domain name generated by the regional endpoint e.g. from d-387h3iudnb.execute-api.us-east-2.amazonaws.com. Once you create the CNAME in your custom domain name, pointing to that url you will get the correct response.

For example your custom domain is api.example.com you should create a CNAME on that subdomain to point to your API Gateway generated domain name (e.g. d-387h3iudnb.execute-api.us-east-2.amazonaws.com). Then you can call your api from api.example.com without problems.

More info in here

api gateway regional custom domain is not working

2 Answers2

Linked