Route 53 + Adv. S3 Flashcards
What does DNS stand for?
What is the primary function of the Domain Name System (DNS)?
How does DNS facilitate internet communication?
Why is DNS an essential component of the internet?
DNS stands for the Domain Name System. The primary function of DNS is to translate human-readable domain names, like www.example.com, into IP addresses, which are numerical identifiers used by computers to locate each other on the internet. DNS serves as a distributed directory that helps browsers, applications, and devices find the correct IP address associated with a given domain, allowing seamless internet communication.
DNS is like a magic helper that makes sure your computer knows where to go on the internet when you type in your favorite website names!
DNS is crucial for the internet because it simplifies how we interact with websites. Without DNS, we’d have to remember and use long strings of numbers instead of easy-to-recall names, making the internet much less user-friendly.
What are some key terminologies associated with DNS?
- Domain name
- IP address
- Namer Server
- DNS Resolver
- Zone
- Top level domain
- Second level domain
- Domain registrar
- Domain records
- Domain Name: A human-readable name associated with an IP address, such as www.example.com.
- IP Address: A numerical identifier for a device on a network, facilitating communication over the internet.
- Name Server: A server that holds DNS records and provides information about a specific domain.
- DNS Resolver: The part of the DNS that receives domain name queries from clients and seeks the corresponding IP addresses.
- Zone: A portion of the DNS namespace managed by a specific authority.
- Top level doamin: .com, .us, .in, .gov …
- Second level domain: amazon.com, google.com,…
- Domain registrar: Amazon Route 53, GoDaddy,…
- Domain records: A, AAA, CNAME…
Understanding these terms is crucial as they collectively define how DNS works. The domain names help us navigate the internet, and DNS servers ensure that our devices can find the correct IP addresses associated with those names.
What is the name of Amazon’s scalable domain name system (DNS) service?
What functionalities does Amazon Route 53 provide in the context of internet domain management?
How does Route 53 contribute to the efficient route of internet traffic
Why is Amazon Route 53 an essential service for website owners and businesses?
Amazon Route 53 is a scalable domain name system (DNS) web service provided by Amazon Web Services.
It offers various functionalities such as domain registration, DNS routing, and health checking of resources.
Route 53 plays a crucial role in efficiently routing internet traffic by translating human-readable domain names into IP addresses, directing users to the correct web servers hosting the requested content. (URL Resolver)
Amazon Route 53 is essential for website owners and businesses because it ensures that people can easily find their websites on the internet.
It’s like having a trustworthy guide that ensures visitors always reach the right place without any confusion.
What are Amazon Route 53 records?
How do Route 53 records contribute to domain management?
Why is understanding Route 53 records important for configuring and optimizing internet domains?
Amazon Route 53 records are configurations that define how the DNS (Domain Name System) should handle requests for a domain.
These records provide crucial information about the domain’s behavior, such as -
* Domain/subdomain Name (eg: example.com)
* Record type (eg; A or AAAA)
* Value (eg; 12.65.46.78)
* Routing Policy (how route 53 responds to queries)
* TTL (amount of time the record cached at DNS resolvers)
Record Types:
* A - maps a hostname to IPv4
* AAAA - maps a hostname to IPv6
* CNAME - maps a hostname to another hostname. (Can’t create a CNAME at the top a DNS namespace)
* NS - Name servers for the hosted zone: Controls how traffic is routed for a domain.
Route 53 Hosted Zones
How do Route 53 Hosted Zones contribute to domain management?
What is the relationship between domain and hosted zone in Route 53?
Why are Route 53 Hosted Zones a critical component in configuring DNS settings?
Route 53 Hosted Zones are containers for DNS records, allowing users to manage the DNS settings for their domains.
- Public Hosted Zones - Records that specify how to route traffic on the internet (public domain names)
- Private Hosted Zones - Records that specify how you route traffic within one or more VPCs (private domain names)
Z - Zone Management: Zones in Route 53 help you manage your domain’s DNS settings and configurations.
O - Organized Records: Within a hosted zone, you organize and maintain DNS records that specify how your domain should function.
N - Navigation Control: Control over the navigation of traffic to and from your domain.
E - Effective Routing Policies: Routing policies within hosted zones to implement effective traffic routing strategies
S - Scalability and Adaptability: At the domain’s infrastructure level, allowing you to easily scale resources and update configurations as your needs evolve.
Route 53 Hosted Zones are super important because they hold the special instructions that guide the internet to the right places.
Understanding and configuring these zones accurately ensures that websites and online services work perfectly, just like they should!
What are CNAME and Alias records in Amazon Route 53?
CNAME -> Canonical Names
How do CNAME and Alias records differ in their functionality?
In what scenarios would you choose CNAME over Alias, or vice versa?
Why is understanding the distinction between CNAME and Alias important in DNS configuration?
CNAME and Alias records in Amazon Route 53 serve similar purposes by allowing one domain to point to another. However, they differ in their usage:
* CNAME Record: It is used for creating aliases from one domain to another, typically for subdomains or non-root domains.
1. CNAME records can’t be used for the root domain (apex domain).
2. Only used for non root domain
-
Alias Record: It functions similarly to a CNAME but is specific to AWS services. Alias records can be used for the root domain and are often preferred when pointing to AWS resources like an S3 bucket, CloudFront distribution, or an Elastic Load Balancer (ELB).
1. Points a hostname to an AWS resource
2. Works for root domain and non root domain
3. Free fo charge
4. Has a native health check capability
5. Always of type A/AAAA for AWS resources (IPv4/IPv6)
6. You can’t set TTL. Done by R53.
CNAME is like a good guide for most places, but Alias is the superhero guide that can go everywhere, even to the main entrance!
Using Alias; You can’t set am ALS record for an EC2 DNS name.
Knowing when to use CNAME or Alias is like choosing the right guide for the right adventure.
Understanding their differences ensures that your DNS settings work perfectly, directing internet traffic accurately.
What are Routing Policies in Amazon Route 53
How do Routing Policies control the distribution of traffic for a domain in Route 53
Can you name a few types of Routing Policies supported by Route 53
Why is understanding Routing Policies crucial for optimizing the performance and availability of web applications?
Routing Policies in Amazon Route 53 are configurations that determine how traffic is distributed among different resources, such as web servers or endpoints. They play a crucial role in controlling the flow of internet traffic for a domain. Several types of Routing Policies are supported, each serving different purposes, including Simple Routing, Weighted Routing, Latency-Based Routing, Failover Routing, Geolocation Routing, and Multivalue Answer Routing.
Routing Policies are like magical guides that make sure everyone reaches the right places on the internet
* Simple
* Weighted
* Failover
* Latency based
* Geolocation
* Multi-Value Answer
Knowing about Routing Policies is like having special maps for the internet that make sure people always reach their destinations quickly and efficiently. Understanding these policies helps ensure that websites and applications run smoothly and are always available to users.
Unlike ELBs, DNS does not route any traffic, it only responds to the DNS queries.
What is the Weighted Routing Policy in Amazon Route 53?
How does the Weighted Routing Policy control the distribution of internet traffic?
When might you choose to use the Weighted Routing Policy in Route 53?
Why is the Weighted Routing Policy important for optimizing resource utilization in web applications?
The Weighted Routing Policy in Amazon Route 53 is a method of distributing internet traffic among multiple resources based on assigned weights.
Each resource (like an endpoint or server) is given a weight percentage, and Route 53 directs traffic proportionally according to these weights.
This allows for controlled testing of new versions or gradual migration of traffic between resources.
The Weighted Routing Policy is important because it lets you control how much traffic goes to different places, allowing for careful testing or gradual changes without overwhelming any particular resource.
This is crucial for optimizing the performance and reliability of web applications during updates or changes.
What are LB and Weighted Routing Policies in the context of AWS?
How do Load Balancers and Weighted Routing Policies differ in distributing internet traffic?
LB -Load Balancer
In what scenarios would you choose to use LB, & Weighted Routing Policy
Why is understanding the distinction between Load Balancers and Weighted Routing Policies important for optimizing the performance of web applications?
Load Balancers:
* Load balancers distribute internet traffic across multiple servers or resources based on factors like server health, ensuring even load distribution for improved performance and reliability.
* They are beneficial for scenarios where high availability and fault tolerance are essential.
Weighted Routing Policies:
* Weighted Routing Policies in Amazon Route 53 distribute traffic based on assigned weights to different resources.
* This allows controlled testing, gradual migration, or specific distribution percentages for different resources.
* Weighted Routing is useful when you want to direct a specific percentage of traffic to different endpoints.
Understanding when to use Load Balancers or Weighted Routing Policies is crucial for optimizing how internet traffic is distributed.
Load Balancers ensure even distribution for reliability
Weighted Routing allows you to control and test different scenarios based on assigned weights.
What is the Latency-Based Routing Policy in Amazon Route 53?
How does the Latency-Based Routing Policy control the distribution of internet traffic?
In what scenarios would you choose to use this Routing Policy ?
Why is the Latency-Based Routing Policy important for optimizing the performance of web applications?
The Latency-Based Routing Policy in Amazon Route 53 directs internet traffic based on the lowest network latency for end-users.
It measures the time it takes for DNS queries to be resolved and directs traffic to the resource with the lowest latency.
This policy is beneficial for optimizing the performance of web applications by minimizing the delay between users and resources.
It can also be associated with health checks.
Super helpful when the latency for users is priority
Latency is based on traffic between users & AWS regions.
The Latency-Based Routing Policy is essential for making sure internet traffic takes the quickest path to resources.
Providing users with a smooth and responsive experience.
What are Route 53 Health Checks?
How do Route 53 Health Checks contribute to the management of internet resources?
Mention purpose of conducting health checks for resources in Route 53?
Why are Route 53 Health Checks important for ensuring the reliability and availability of web applications?
Route 53 Health Checks are a feature in Amazon Route 53 that monitors the health and performance of internet resources, such as servers or endpoints.
If a resource fails a health check, Route 53 can automatically reroute traffic away from the unhealthy resource, helping maintain high availability and reliability.
- Multiple health checker requests come from all over the world.
- 2XX or 3XX response from the health checker is healthy.
- Returns healthy if >18 % of the checks return 2XX or 3XX.
- At a time, only 256 health checks can be handled.
- All the health checkers live in the public network. Hence, it only checks public end-points.
- To perform health checks for private end-points. One has to colloborate health checks with cloudWatch alarms to do so.
HTTP health checks are only for public resources for DNS failovers
Route 53 Health Checks are super important because they ensure that internet resources are in good shape. If something isn’t right, they can quickly guide internet traffic away from the problem, making sure websites and applications are always available and working well.
What is the Failover Routing Policy in Amazon Route 53?
How does the Failover Routing Policy control the distribution of internet traffic?
In what scenarios would you choose to use the Failover Routing Policy in
Why is the Failover Routing Policy important for ensuring the availability and reliability of web applications?
The Failover Routing Policy in Amazon Route 53 is a configuration that directs internet traffic to a designated resource (such as a backup server) when the primary resource becomes unhealthy.
It allows users to set up a primary resource and a backup resource, ensuring that if the primary resource fails a health check, traffic is automatically redirected to the backup.
This policy is crucial for maintaining high availability and minimizing downtime.
Failover Routing is as a magical switch; ensures a backup for failures
The Failover Routing Policy is important because it acts like a safety net for internet resources. If the main resource isn’t working properly, it quickly switches to a backup, ensuring that websites and applications are always available and reliable.
What is the Geolocation Routing Policy in Amazon Route 53?
Why is the Geolocation Routing Policy important for optimizing the performance of web applications?
How does Geolocation Routing Policy control the distribution of traffic?
In what scenarios would you choose to use the Geolocation Routing Policy in Route 53?
The Geolocation Routing Policy in Amazon Route 53 directs internet traffic based on the geographical location of the user.
It allows users to define specific routing configurations for different regions or countries.
This policy is useful when tailoring the user experience or directing traffic to region-specific resources based on the geographical location of the user.
Routing based on user’s location based on IP address
The Geolocation Routing Policy is important because it lets websites and applications provide a customized experience based on where users are in the world.
This ensures that users get the fastest and most relevant content, optimizing their overall online experience.
What is the Geoproximity Routing Policy in Amazon Route 53?
How does the Geoproximity Routing Policy control the distribution of internet traffic?
In what scenarios would you choose to use Geoproximity Routing Policy
Why is the Geoproximity Routing Policy important for optimizing the performance of web applications?
The Geoproximity Routing Policy in Amazon Route 53 directs internet traffic based on the physical proximity of the user to AWS resources.
It uses geographic locations of the user and the AWS resources to determine the best routing.
This policy is particularly useful when optimizing performance by directing users to the nearest resources or data centers, reducing latency and improving overall user experience.
- Route traffic to your resources based on the geographic location of users and resources.
- Ability to shift more traffic to resources based on the defined bias.
- Resources can AWS resources or Non-AWS resources
- You must use Route 53 traffic flow (advanced) to use this feature.
The Geoproximity Routing Policy is important because it makes sure that internet traffic is directed to the nearest resources, reducing delays and making websites and applications load faster.
This is crucial for providing users with an optimal and enjoyable online experience.
What is the Multi-Value Routing Policy in Amazon Route 53?
How does the Multi-Value Routing Policy control the distribution of internet traffic?
In what scenarios would you choose Multi-Value Routing Policy?
Why is the Multi-Value Routing Policy important for optimizing the performance of web applications?
The Multi-Value Routing Policy in Amazon Route 53 allows users to configure multiple values for a DNS record, such as:
- IP addresses.
It responds to DNS queries with a random selection of values, distributing traffic across all the configured resources.
This policy is useful when optimizing performance by providing fault tolerance and load balancing across multiple resources.
- Used when routing traffic to multiple resources.
- Route 53 returns multiple values/resources.
- Can be associated with health checks.
- Uto 8 healthy records are returned for each multi-value query.
- Multi-value routing is not a substitute for having an ELB.
The Multi-Value Routing Policy is important because it helps distribute internet traffic randomly across multiple resources.
This not only ensures fault tolerance but also provides a balanced load on different servers or endpoints, optimizing the overall performance of web applications.
