2024년 SAA-C03 자격증 준비하면서 필요한 노트 정리했습니다
강의는 유데미 "Ultimate AWS Certified Solutions Architect Associate SAA-C03" 통해 공부했습니다
https://www.udemy.com/course/aws-certified-solutions-architect-associate-saa-c03
같이 공부해서 합격해보자구요 !
Section 10 : Route 53
101. What is a DNS ?
- domain name system - translate hostnames -> machine ip address
- DNS = backbone of the internet
- domain registrar : amazon route 53, 가비아
- dns records : cname, ns
- zone file : contains dns records
- name servers : resolves dns queries
- top level domain tld : .com, .in. co.kr
- second level domain sld : amazon.com
- dns steps
- local dns server
- root dns server
- tld dns server
- sld dns server
- back to local pc
- local pc then has the specific ip address on where to access the server
102. Route 53 Overview
- A highly available, scalable, fully managed dns
- route 53 is also domain registrar
- only aws service providing 100% availability sla
- record types
- a - maps a hostname to ipv4
- aaaa - maps to ipv6
- cname - maps hostname to another hostname
- ns - name servers for the hosted zone
- hosted zones
- public hosted zones - contains records that specify how to route traffic on the internet
- private hosted zones - route traffic within one or more vpcs (private domain names)
- you pay 50 cent per month per hosted zone, 12 dollar per year, its not free for free-tier
106. Route 53 - TTL
- ttl - time to live, dns cache live period on client side
- high ttl : less traffic to route 53 but may have outdated records
- low ttl : more traffic to route 53, which means more costs will be charged, records are oudated for less period and easy to change dns records
107. Route 53 CNAME VS ALIAS
- cname - only for non root domain
- alias - works root domain & non root domain, free of charge and contains native health checks
108. Routing Policy - simple
- dns does not route any traffic, it only responds ot the dns queries, its not a load balancer
- simple
- can specify multiple values in the same record, if multiple values are returned, a random one is chosen by the client
109. Routing Policy - weighted
- control the % of the requests that goes to each specific resource
- ex. 70, 20, 10, weight dont need to sum up to 100, it is relative to each other
- this is useful for controling traffic of new application version tests for maybe 10 percent of its users etc
110. Routing Policy - latency-based
- redirect to the resource that has the latest latency close to user
- helpful when latency for users is a priority
111. Routing 53 - Health Checks
- all health checkers are outside the vpc, hence cant check private endpoints
- you can create cloudwatch metric and assoicate with alarm and health checker will check the cloudwatch alarm to see if private endpoints are accessible or not
113. Routing Policy - Failover
- active passive -> if active one fails it will redirect the tranascation to passive instance hence a failover
114. Routing Policy - Geolocation
- its different from latency-based
- this routing is based on user location
115. Routing Policy - Geoproximity
- using a geolocation based routing, if you need to shift more traffic to a specific region, you would use this geoproximity route to handle the traffic
- increasing the bias will increase the traffic
- decreasing the bias will decrease the traffic
116. Routing Policy - ip-based routing
- routing based on clients ip address
- private a list of cidr for your clients
- ex. route end users from a particular ip address to a specifc endpoint
117. Routing Policy - multi value
- multiple values.resources
같이 파이팅해서 합격해봅시당 ㅎㅎ
저는 24년 10월 중순에 시험 볼 예정입니다 ! (후기 남기도록 하겠습니다 후후)
토니이츠얼랏 : 네이버 블로그
너무너무너무 많이 먹는 토니입니당 :) 개발 블로그도 방문해주세용 (제꺼에요 :p) https://tonyzorz.tistory.com/
blog.naver.com
