Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

AWS SOA > ROUTE 53 > Flashcards

ROUTE 53 Flashcards

1
Q

What is a Zone File

A

a Zone file a database that contains all the DNS information of a domain

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Top Level Domains, with Examples

A

A top-level domain (TLD) is one of the domains at the highest level in the hierarchical Domain Name System of the Internet after the root domain.

.com, .io, .net

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

When a Domain is Registered, two things

A
  1. Route 53 checks if the domain is available
  2. Creates a Zone File for the domain(a database that contains all the DNS information of a domain)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Private and Public Hosted Zones

A

Public - Records are accessible from anywhere
Private - Records are only accessible from within vpc, also good for hosting sensitive private DNS records

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Public Hosted Zone

A

Public Hosted Zone is a DNS Database. Zone files hosted by Route53 on Public Name Servers

Notes from AWS
A public hosted zone is a container that holds information about how you want to route traffic on the internet for a specific domain, such as example.com, and its subdomains (acme.example.com, zenith.example.com). You get a public hosted zone in one of two ways:

When you register a domain with Route 53, we create a hosted zone for you automatically.
When you transfer DNS service for an existing domain to Route 53, you start by creating a hosted zone for the domain. For more information, see Making Amazon Route 53 the DNS service for an existing domain.
In both cases, you then create records in the hosted zone to specify how you want to route traffic for the domain and subdomains. For example, you might create a record to route traffic for www.example.com to a CloudFront distribution or to a web server in your data center. For more information about records, see Working with records.

This topic explains how to use the Amazon Route 53 console to create, list, and delete public hosted zones.

A public hosted zone is a container that holds information about how you want to route traffic on the internet for a specific domain, such as example.com, and its subdomains (acme.example.com, zenith.example.com). You get a public hosted zone in one of two ways:

When you register a domain with Route 53, we create a hosted zone for you automatically.
When you transfer DNS service for an existing domain to Route 53, you start by creating a hosted zone for the domain. For more information, see Making Amazon Route 53 the DNS service for an existing domain.
In both cases, you then create records in the hosted zone to specify how you want to route traffic for the domain and subdomains. For example, you might create a record to route traffic for www.example.com to a CloudFront distribution or to a web server in your data center. For more information about records, see Working with records.

This topic explains how to use the Amazon Route 53 console to create, list, and delete public hosted zones.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

When you register a Hosted Zone

A

Route 53 Allocates 4 public Name Servers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Accessing Route 53

A

Instances within VPC can query the Hosted Zone using Route 53resolver+2, provided the VPC DNS is enabled

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Split View

A

Hosted Zone Split view allows for the use of thesame Name Server(Domain name) for both private and public view with each view resolving to a differnt Record. Both private users(from VPC) and Public users use thesame DNS name to access the NS but get customized Records.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Alias Record

A

This record resolves a domain name to aws services that do not have ip Addresses but rather issues naked domain

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Simple Routing Heath check settings

A

Does not support health checks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Healthy Healthcheck Threshold

A

Any report of threshold above 18% is considered healthy

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Failover Routing Policy

A

For Active-Passive architecture. Eg A dynamic website using s3 as backup

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Websites on Ec2 Instance tips

A

Runing a Website or DB on EC2, you must use an Elastic IP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Failover records steps

A
  1. Create the twoRecords(Websites)
  2. Ensure the Website on an EC2 Instance has an elastic IP address.
  3. Setup the Static website on S3
    - Create bucket and upload files
    - Enable Static web Hosting
    - Unblock public view
    - Add Bucket Policy(Remembe Resource ARN must be included in the Policy.
  4. Create Health checks on Route 53 Hosted Zones for primary website on the Main server/Record ie, EC2(Elastic IP)
  5. Create failover record on route 53 for Primary Record and Secondary S3(must have thesame Domain Name of our Main Domain resgistered in Route 53
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Hosted Zone

A

A hosted zone is a container for records, and records contain information about how you want to route traffic for a specific domain, such as example.com, and its subdomains (acme.example.com, zenith.example.com). A hosted zone and the corresponding domain have the same name. There are two types of hosted zones:

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Health checks behavior with weighted records

A

In weighted record, the % allocated weight stays intact in spite of any record failing health check. Weight values are not automatically altered to make up for any failed record.

17
Q

Weighted Routing use cases

A
  1. As a simple Load Balancer to split workload according to the strength of the server.
  2. Used to test workloads before they are scaled
  3. It is used along with TTL to control dedicated access to certain servers
18
Q

Latency Routing

A

Note that this routing type is not Realtime. It does not account for Local Network Issues. It only reports regional recent latencies.

19
Q

Geolocation Tagging

A

Geolocation Tagging doesn’t return Closest records. It only returns relevant records to a particular Location.

In this type of routing, records of certain locations are tagged to specific locations. User requests are therefore forwarded to records based on the source Location. Thereby supplying specific records to specific requests coming from a particular region.

This is effective in scenarios where compliance is priority.

20
Q

Geolocation Routing process

A

It checks records in steps before responding to the request
Steps
Search and return record if record is in steps
Elif;
Steps;
1. Checks Region
2. Checks country
3. Checks Continent
Else;
Return; Not found

21
Q

AWS Edge Location

A

A few Racks hooked up in a shared or dedicated data center made up of storage and Network layers used for caching data

22
Q

Cloud front Distribution

A

A configuration file for cloudfront

23
Q

Cloudfront caching

A

Read only caching

Writes are performed only via direct origin writes.

24
Q

Cloudfront caching Query process

A
  • EdgeLocations
  • Regional Edge Center
  • Origin

AWS SOA (47 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions