api gateway regional custom domain is not working

14
votes

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.

1
amazon-web-servicesaws-api-gateway
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
have you had any luck with this? – Victor
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

1 Answers

23
votes

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