Networking & Content Delivery Flashcards
What it the main purpose of Route 53
Routing Internet Traffic to your Website or Web Application
Route 53 Health Checks
Whats steps are required for route53 to route Internet Traffic to your Website or Web Application
- Use the Route 53 console to register a domain name and configure Route 53 to route internet traffic to your website or web application.
- After you register your domain name, Route 53 automatically creates a public hosted zone that has the same name as the domain.
- To route traffic to your resources, you create records, also known as resource record sets, in your hosted zone.
- You can create special Route 53 records, called alias records, that route traffic to S3 buckets, CloudFront distributions, and other AWS resources.
◦ Name – name of the record corresponds with the domain name or subdomain name that you want Route 53 to route traffic for.
◦ Type – determines the type of resource that you want traffic to be routed to.
◦ Value
How do you route internet traffic to AWS resources?
• To route traffic to your resources, you create records, also known as resource record sets, in your hosted zone.
• You can create special Route 53 records, called alias records, that route traffic to S3 buckets, CloudFront distributions, and other AWS resources.
• Each record includes information about how you want to route traffic for your domain, such as:
◦ Name – name of the record corresponds with the domain name or subdomain name that you want Route 53 to route traffic for.
◦ Type – determines the type of resource that you want traffic to be routed to.
◦ Value
What values can you use to specify how a health check work in route 53?
◦ Create a health check and specify values that define how you want the health check to work, such as:
▪ The IP address or domain name of the endpoint that you want Route 53 to monitor.
▪ The protocol that you want Route 53 to use to perform the check: HTTP, HTTPS, or TCP.
▪ The request interval you want Route 53 to send a request to the endpoint.
▪ How many consecutive times the endpoint must fail to respond to requests before Route 53 considers it unhealthy. This is the failure threshold.
◦ You can configure a health check to check the health of one or more other health checks.
◦ You can configure a health check to check the status of a CloudWatch alarm so that you can be notified on the basis of a broad range of criteria.
Which policy in route 53 allows routing of internet traffic to a single resource that performs a given function for your domain?
• Simple routing policy – route internet traffic to a single resource that performs a given function for your domain. You can’t create multiple records that have the same name and type, but you can specify multiple values in the same record, such as multiple IP addresses.
To configure active-passive failover in route 53 which routing policy would you use?
Failover routing policy – use when you want to configure active-passive failover.
To route internet traffic to your resources based on the location of your users which routing policy would you use?
Geolocation routing policy – use when you want to route internet traffic to your resources based on the location of your users.
To route internet traffic based on the location of your resources and optionally, shift traffic from resources in one location to resources in another you’d use which routing policy?
• Geoproximity routing policy – use when you want to route traffic based on the location of your resources and, optionally, shift traffic from resources in one location to resources in another.
◦ You can also optionally choose to route more traffic or less to a given resource by specifying a value, known as a bias. A bias expands or shrinks the size of the geographic region from which traffic is routed to a resource.
◦ The effect of changing the bias for your resources depends on a number of factors, including the following:
▪ The number of resources that you have.
▪ How close the resources are to one another.
▪ The number of users that you have near the border area between geographic regions.
You want to route traffic to the resource that provides the best latency, which policy would you use?
Latency routing policy – use when you have resources in multiple locations and you want to route traffic to the resource that provides the best latency
Why use a weighted routing policy?
- Weighted routing policy – use to route traffic to multiple resources in proportions that you specify.
- When you register a domain or transfer domain registration to Route 53, it configures the domain to renew automatically. The automatic renewal period is typically one year, although the registries for some top-level domains (TLDs) have longer renewal periods.
- When you register a domain with Route 53, it creates a hosted zone that has the same name as the domain, assigns four name servers to the hosted zone, and updates the domain to use those name servers.
What is the purpose of DNS records?
• Create records in a hosted zone. Records define where you want to route traffic for each domain name or subdomain name. The name of each record in a hosted zone must end with the name of the hosted zone.
What a are the differences between CNAME and Alias records?
CNAME Records
- You can’t create a CNAME record at the zone apex.
Route 53 charges for CNAME queries. - A CNAME record redirects queries for a domain name regardless of record type.
- A CNAME record can point to any DNS record that is hosted anywhere.
- A CNAME record appears as a CNAME record in response to dig or Name Server (NS) lookup queries.
- An alias record appears as the record type that you specified when you created the record, such as A or AAAA.
Alias Records
- You can create an alias record at the zone apex. Alias records must have the same type as the record you’re routing traffic to.
- Route 53 doesn’t charge for alias queries to AWS resources.
- Route 53 responds to a DNS query only when the name and type of the alias record matches the name and type in the query.
- An alias record can only point to selected AWS resources or to another record in the hosted zone that you’re creating the alias record in.
Route 53 supported record types?
- A Record Type – the value for an A record is an IPv4 address in dotted decimal notation.
- AAAA Record Type – the value for a AAAA record is an IPv6 address in colon-separated hexadecimal format.
- CAA Record Type – lets you specify which certificate authorities (CAs) are allowed to issue certificates for a domain or subdomain.
- CNAME Record Type – a CNAME Value element is the same format as a domain name.
- MX Record Type – each value for an MX record actually contains two values, priority and domain name.
- NAPTR Record Type
- NS Record Type – identifies the name servers for the hosted zone. The value for an NS record is the domain name of a name server.
- PTR Record Type – is the same format as a domain name.
- SOA Record Type – provides information about a domain and the corresponding Amazon Route 53 hosted zone.
How do health check evaluate the health of an endpoint?
Each health checker evaluates the health of the endpoint based on two values:
◦ Response time
◦ Whether the endpoint responds to a number of consecutive health checks that you specify (the failure threshold)
What can 3 things can a health check be setup to monitor?
Each health check that you create can monitor one of the following:
◦ The health of a specified resource, such as a web server
◦ The status of other health checks
◦ The status of an Amazon CloudWatch alarm
Which AWS tool can you use to collect metrics on healthchecks?
- You can use Amazon CloudWatch metrics to see the number of DNS queries served for each of your Route 53 public hosted zones. With these metrics, you can see at a glance the activity level of each hosted zone to monitor changes in traffic.
- You can monitor your resources by creating Route 53 health checks, which use CloudWatch to collect and process raw data into readable, near real-time metrics.
- Log API calls with CloudTrail
Purpose of CloudFront?
A web service that speeds up distribution of your static and dynamic web content to your users. A Content Delivery Network (CDN) service
How does CloudFront deliver content?
It delivers your content through a worldwide network of data centers called edge locations. When a user requests content that you’re serving with CloudFront, the user is routed to the edge location that provides the lowest latency, so that content is delivered with the best possible performance.
◦ If the content is already in the edge location with the lowest latency, CloudFront delivers it immediately. ◦ If the content is not in that edge location, CloudFront retrieves it from an origin that you’ve defined
Which protocols does CloudFront support?
CloudFront supports the WebSocket protocol as well as the HTTP protocol with the following HTTP methods: ◦ GET ◦ HEAD ◦ POST ◦ PUT ◦ DELETE ◦ OPTIONS ◦ PATCH.
What are the different CloudFront Origins?
◦ Using S3 buckets for your origin – you place any objects that you want CloudFront to deliver in an S3 bucket.
◦ Using S3 buckets configured as website endpoints for your origin
◦ Using an mediastore container or an mediapackage channel for your origin – you can set up an S3 bucket that is configured as a MediaStore container, or create a channel and endpoints with MediaPackage. Then you create and configure a distribution in CloudFront to stream the video.
◦ Using EC2 or other custom origins – A custom origin is an HTTP server, for example, a web server.
◦ Using CloudFront Origin Groups for origin failover – use origin failover to designate a primary origin for CloudFront plus a second origin that CloudFront automatically switches to when the primary origin returns specific HTTP status code failure responses.
