Amazon Route 53

Amazon Route 53 has a simple UI with everything you need right in front of you. When you add a new record, the response time is super fast. Support for elastic DNS is also fantastic, as setting anything like that up manually requires knowledge, whereas Route53 provides it ready-made availability.

Amazon Route 53 is an excellent tool for DNS routing that is simple to set up. Setting up your domain with DNS servers and DNS routing in minutes takes virtually no time. Route 53 is ideal for all sizes of businesses, all types of industries, and all regions of countries.

Our backend services run in AWS, and we need public domain to expose the services. The services are running in different geo locations as we have end users globally. But we would like to provide one single domain to end users. With the routing features from Amazon Route 53, we are able to route the requests to nearest location from the user, which reduces latency and improves user experience.

Ease of use and management of the amazon route 53 that is our main benefit. Our current solution was not cloud based and it would affect us geographically. But Route 53 being a cloud service has greatly helped us in that space. We use it for managing the external DNS services within our organization.

We have been using Amazon Route 53 in order to redirect our end users to our applications, using their capability of translating human language to our IP addresses. Before using Route 53, we were facing a lot of issues regarding routes and DNS which now is much easier to set up and follow up.

We use Amazon Route 53 to provide public DNS services for several domains for our public websites, remote access with health checks, and for other common services. We needed a global and reliable provider that had a lot of functionality and could work well with our public website, which is also hosted on AWS.

Highly Available, scriptable DNS zone management. We had issues with DOS on smaller providers (Ultra, Dyn) and Amazon Route 53 was able to handle DDOS against our zones better.

We use AWS Route 53 as the DNS management solution for ~12 years. We have over 800+ domain entries being managed over there. These include the tools as below:

1. API Endpoints that process over 100M API calls a day.
2. Web-Portal for configuration management used by 20K business users.
3. Web-hooks exposed to the external world for sending DLR notifications for the marketing messages that we send out (>100M messages per day).

I am using amazon rote 53 as a delegated Nameserver from my primary DNS server. This is acting as a backup DNS incase if the primary goes down

Amazon Web Service (AWS) Route 53 offers seamless Domain Name Services Offering , Route53 was used to register company domains in the cloud so that cloud based workloads such as EC2 instance and Applications can be integrated and joined with customer domains. For certain applications route 53 DNS was used to control the traffic across different regions.

Amazon Route 53 is great place to manage your all domains and sub domains. You can easily add and manage your all domains. Also making changes are so easy and whatever you change or add records same like TXT, DNS, MX and more, it affects so quickly and you do not have to wait so long time.

We use Route53 as the main domain provider in our company. Although we don't purchase the domain in there for legal reasons, we do delegate all of them to Route53 to manage them directly within the AWS console, or through the API or even through Terraform. We currently have hundreds of hosted zones, and ten of thousands of records in there.

We use this Amazon software to manage incoming customer messages/ requests on Amazon orders for our product. It enables us to connect with these third-party customers (we usually wouldn't be able to, since it's a separate shipping system from our DTC business). I mainly use it to access Amazon orders and speak with customers.

We use Amazon Route 53 to host a few websites and their content. It is a good option for people who seek to start a website quickly and attach a domain name to it and host HTML5 and static content. You don't need to look for a server. If you are already using Amazon - it is a very good option.

Route 53 is used as our primary Domain Name Service (DNS) which exposes our products to our users online. Unlike other DNS providers, Route 53 is specialized to work within Amazon Web Services (AWS) to make exposing endpoints across services as seamless as possible. Route 53 also helps quickly switch routing for our red/green deployments making sure our customers have a great experience when using our services during updates.

Route 53 is quite powerful and more flexible than the managed DNS our registrar provides. It allows us to easily smooth over the many domain transfers we have to do as part of web hosting by allowing easy, longer term off-site DNS servers. We also use it with our own web servers, and Route 53 provides a lot of great features for load balancing.

I have worked with AWS Route 53 in all the three of my Organizations in which I worked. Route 53 plays major role when it comes to create and serve the Website all over the world for DNS when created through Amazon web services also when you are website is hosted in less popular cloud providers. One best thing is we can use Route 53 service alone from AWS even though our website is hosted in any other Cloud Service Provider. And, as usual route 53 offers all types of Routing type which you can expect of also the cost is competitive for the scale it provides.
The main reason for backing up this service as per my advice it would be it interacts with anything service provider and setting up is kinda of easy also there isn't negligible downtime.

Route 53 means the automation of a lot of stuff we did manually before. It's used by our Infrastructure team and some other small teams when in development. The business problems that it solves were related to speed in new deployments of entries, change entries, set up new domains, and being faster than before.

Amazon Route 53 is being used at our company as the default DNS service. This service is used both by the technical department for production and by the marketing team for the website.

As part of our Cloud migration to AWS we have started using Route 53. Being able to programmaticaly build all aspects of the deployment in general and for route 53 in particular is a life saver. Being part of the same ecosystem make deploying so much easier... As we move all on-prem to AWS, and DNS is essential, Route 53 we need to rely on R53 and it delivers.

We're using Route53 to manage all of our internal DNS entries within our company. It has allowed us to map URLs to many different IP addresses and is easier to keep track of what address points go to which server.

Route 53 provides a nice centralized location for managing our domains. It makes it easy to assign DNS records to various AWS instances, elastic load balancers or aliases to other servers not located inside AWS infrastructure. Route 53 has had great availability and ensured our DNS setup is relatively painless and not needing concern.

Route53 is an easily accessible and simple DNS service that's integrated with AWS. We use Route53 for any web applications that we deploy and I have used Route53 for all of my personal projects that need DNS routing. While it does lack some control when routing traffic to resources outside of AWS, it solves any tangible need for AWS-hosted applications.

DNS is a core piece of any internet backbone. Route 53 provides distributed and resilient DNS services with little effort. Moving to Route 53 is as simple as either updating your domain's name server records, or to move the domain to AWS. Route 53 provides a simple and inexpensive mechanism for managing and serving DNS traffic.