Route 53 is used for delivering data transfer to clients and AWS services that are in the EC2s. It is also used for traffic management through various routing policies such as simple routing, latency-based routing, geolocation routing, and failover routing.
AWS Senior Consultant at a tech services company with 51-200 employees
Consultant
Top 10
2024-10-16T08:30:00Z
Oct 16, 2024
I use Route 53 as a global naming service. For anyone to access services with a recognizable name like PeerSpot dot com, Route 53 is a necessity. It is utilized not only for public access but also as a private aliasing service to secure and protect services. Additionally, Route 53 offers a DNS firewall to safeguard against DNS vulnerabilities.
Software Engineer DevOps at a financial services firm with 51-200 employees
Real User
Top 10
2024-03-05T14:02:41Z
Mar 5, 2024
Our primary use case for Amazon Route 53 revolves around its robust domain name system (DNS) management capabilities, supporting a diverse set of parameters and records within our environment. We extensively use Route 53 for managing various record types, including A records, MX records, and CNAME records.
Our primary focus is on migrating from an on-premises infrastructure to a cloud-based solution. This entails handling multiple versions of modern applications, with a specific emphasis on cloud support, especially for API functionalities.
Our company uses the solution for DNS services. We purchase domains, create load balancers, set provisions, host websites, and manage how internet traffic routes to websites. The solution handles all DNS queries and translates friendly domain names to numeric IP addresses.
We use Amazon Route 53 for DNS management. We're doing continuous evaluations of our policies on AWS, which is another reason why we're using Amazon Route 53. The solution is deployed on a private cloud. We're a startup, so less than 100 people are using this solution.
Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service. It is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. Amazon Route 53 is fully compliant with IPv6 as well.
Route 53 is used for delivering data transfer to clients and AWS services that are in the EC2s. It is also used for traffic management through various routing policies such as simple routing, latency-based routing, geolocation routing, and failover routing.
I use Route 53 as a global naming service. For anyone to access services with a recognizable name like PeerSpot dot com, Route 53 is a necessity. It is utilized not only for public access but also as a private aliasing service to secure and protect services. Additionally, Route 53 offers a DNS firewall to safeguard against DNS vulnerabilities.
I use the solution in my company to route our applications to different domain names and IPs.
I use the solution in my company for internet monitoring.
Amazon Route 53 provided the solution we needed to manage servers.
We use Amazon Route 53 for DNS mapping.
I use the solution in my company to create or set up DNS for some projects.
Our primary use case for Amazon Route 53 revolves around its robust domain name system (DNS) management capabilities, supporting a diverse set of parameters and records within our environment. We extensively use Route 53 for managing various record types, including A records, MX records, and CNAME records.
The solution is used for DNS management of applications running primarily on AWS.
Our primary focus is on migrating from an on-premises infrastructure to a cloud-based solution. This entails handling multiple versions of modern applications, with a specific emphasis on cloud support, especially for API functionalities.
The product is a DNS service for AWS. It manages my DNS resolutions on the internet.
We use the product for DNS load balancing and WAF.
We are using Amazon Route 53 for DNS management.
Our company uses the solution for DNS services. We purchase domains, create load balancers, set provisions, host websites, and manage how internet traffic routes to websites. The solution handles all DNS queries and translates friendly domain names to numeric IP addresses.
Our primary use case is as a tool for projects that require managing the DNS.
We use Amazon Route 53 for DNS management. We're doing continuous evaluations of our policies on AWS, which is another reason why we're using Amazon Route 53. The solution is deployed on a private cloud. We're a startup, so less than 100 people are using this solution.