19 engineers on Hacker News describe using Amazon Route 53 first-hand: 5 endorse it, 2 regret it, 2 are mixed.
“We moved to Route 53; our expected bill is around $5K/year.”
endorse · production · PaywallBuster · 2026-10-10 · source ↗ · wrong label?“The hoops you have to jump through with both of them to host a simple website with their CDNs is embarrassing.”
regret · production · jillesvangurp · 2026-09-08 · source ↗ · wrong label?“Need to get hold of someone in Route53 no problem they are on the call this week.”
endorse · production · sparc24 · 2023-10-11 · source ↗ · wrong label?“I do use an AWS service for my side project: Route53. It costs me less than $2/mo and provides a quick, easy, and powerful way to manipulate DNS records”
endorse · personal · cookiecaper · 2016-04-06 · source ↗ · wrong label?“we just spun up a Route53 zone, exported our zone from DNSimple, imported to Route53, and hand-migrated our ALIAS records”
mixed · production · whafro · 2014-12-01 · source ↗ · wrong label?“Amazon's Route53 supports aliases, but via a 301 redirect, which doesn't work in an SSL context (without browser warnings).”
mixed · production · whafro · 2014-12-01 · source ↗ · wrong label?“Route 53 Anycast is outstanding. For now I see Amazon for global DNS infrastructure”
endorse · production · amadeuspzs · 2013-12-29 · source ↗ · wrong label?“We're doing some initial testing with Route 53 (Amazon's DNS services) and so far so good, with great flexibility and a nice API into DNS.”
endorse · personal · blantonl · 2012-12-19 · source ↗ · wrong label?“We also aren't going to use Route53, because we learned last night that the API for that can go down and you can get stuck with bad DNS records.”
regret · production · explodingbarrel · 2012-06-30 · source ↗ · wrong label?“The monthly AWS bill is roughly 5 USD and consists of Route53 only!”
neutral · personal · logotype · 2024-05-02 · source ↗ · wrong label?“These are the services we used.”
neutral · production · scarface74 · 2020-12-20 · source ↗ · wrong label?“we have a rule that you can't create a route53 hosted zone without also enabling logging for the zone.”
neutral · production · arkadiyt · 2020-12-12 · source ↗ · wrong label?“When we migrated DNS to route53 in early 2019 we discussed moving registration as well.”
neutral · production · MrCharismatist · 2020-11-06 · source ↗ · wrong label?“some DNS record in Route 53 went missing, and that silently prevents certificate renewal.”
neutral · production · jrockway · 2019-12-13 · source ↗ · wrong label?“the standard auxiliary services like CW, SNS, Route53, S3, CF, X-Ray, etc.”
neutral · production · 1.5 yr · not_kurt_godel · 2018-06-23 · source ↗ · wrong label?“handles DNS to Route53 (and the VPC) so <service>.farmlogs "just works"”
neutral · production · whalesalad · 2017-11-25 · source ↗ · wrong label?“It was ultimately faster than Route 53 and Google Cloud (the path we ended up going).”
neutral · personal · thefarseeker · 2017-01-10 · source ↗ · wrong label?“AWS S3 for static storage + Route 53 for static websites”
neutral · production · bikamonki · 2015-02-10 · source ↗ · wrong label?“We used Route53 latency based routing to route traffic to that dedicated servers + Nginx + LUA.”
neutral · production · hurrycane · 2014-03-05 · source ↗ · wrong label?