Aws-cli: route53domains only has one region

[atward]

route53domains is a global service and calls should be mapped through to the correct endpoint.

$ aws route53domains list-domains

Could not connect to the endpoint URL: "https://route53domains.ap-southeast-2.amazonaws.com/"
$ python -c 'import boto.route53.domains;print boto.route53.domains.regions()'
[RegionInfo:us-east-1]
$ aws --region us-east-1 route53domains list-domains
{
    "Domains": []
}
$ aws --version
aws-cli/1.7.31 Python/2.7.6 Darwin/14.3.0

Should config.default.region be used when there's only one endpoint?

[kyleknap]

According to the docs, the route53domains api does not have a global endpoint. It is just one regional endpoint, as you noted. The issue with defaulting to this single regional endpoint is that if route53domains ever expands into a new region, this logic will be broken because the new endpoint will never be used.

I do see that the error message is not too helpful, and that is something that we are looking to improve.

Let me know if you have any more questions.

[kyleknap]

Closing issue. Please reopen if you have any more questions or comments.

[FBosler]

For everybody coming across this thread when trying to use the route53domains API endpoint.

You will have to explicitly specify us-east-1 as the region like aws --region us-east-1 route53domains list-domains even if you only have domains in Europe for example.

[Pluies]

Thanks @FBosler ! I use eu-west-1 as default, and was running into the same issue in the AWS Go SDK, which showed up as:

RequestError: send request failed
caused by: Post "https://route53domains.eu-west-1.amazonaws.com/": dial tcp: lookup route53domains.eu-west-1.amazonaws.com: no such host

Setting the region to us-east-1 for this session fixed this. 👍