4 ms·
on www.name.com a .rest domain costs 43$ a year which is four times the cost of a .com domain. Also you might not be able to transfer the .rest domain to AWS to
by giorgioz 7y ago
on www.name.com a .rest domain costs 43$ a year which is four times the cost of a .com domain.
Also you might not be able to transfer the .rest domain to AWS to manage it with AWS Route 53.
A simpler and cheaper approach would be to create a subdomain and/or a subpath
1) api.example.com (SUBDOMAIN)
2) www.example.com/api (SUBPATH)
3) api.example.com/api (SUBDOMAIN AND SUBPATH)
- rumanator 7y agoThe subdomain approach is the more appropriate because: * DNS routing * Can control/fine tune CORS * Avoid mixing up path routing with other interfaces/services * It's more coherent (i.e., page served with www.example.com and REST API at api.example.com)
- giorgioz 7y agoyes I agress subdomain is definitely better than subpath overall. I personally use the subdomain AND subpath approach for a api and an api service (api.example.com/api) This way I have the separate DNS but if I want I can add the API service as a subpath to www.example.com/api using AWS API Gateway and avoid an extra round trip call to the DNS and CORS.
- etsync 7y agoThanks for raising the possible concern with R53. Because of this, I reached out to AWS Support and they confirmed if you have this extension and want to use it with an AWS offering, you can use any domain extension you'd like, even a crazy obscure one (like .ycomb). But you can't buy and host this domain extension at R53 currently.