Please enable JavaScript.

Coggle requires JavaScript to display documents.

Route 53 - Coggle Diagram

- - - - Authoritative
      - Non-Authoritative
- - - - A
        
        Maps hostname to IPv4
      - AAAA
        
        Maps hostname to IPv6
      - CNAME
        
        Maps hostname to another hostname
        
        Target domain must have a A / AAAA record
        
        Can't create for top node of DNS namespace (Zone Apex)
        
        Can't create for example.com, but can for www.example.com
      - NS
        
        Name Servers for the Hosted Zone
        
        Control how traffic is routed for domain
    - - CAA, DS, MX, etc.
- - - - To single resource
      - Can specify multiple values
        
        Client chooses random one
      - Only one AWS resource if Alias
      - No health check support
    - - % of requests to each resource
      - Each record has relative weight
      - DNS records must have same name and type
      - Supports health checks
      - Use cases
        
        Load balance regions
        
        Test new app versions
      - Assign 0 weight to stop routing to resource
    - - Uses health checks
    - - Direct to resource with least latency
      - Latency based on traffic between user and AWS regions
      - Supports health checks for failover
    - - Based on user location
      - Based on Continent / Country / US State
      - Overlap selects most precise location
      - Default record must be created (used if no match)
      - Use cases
        
        Website localization
        
        Restrict content distribution
        
        Load balancing
      - Supports health checks
    - - When routing to multiple resources
      - Multiple values returned (max 8)
      - Supports health checks
      - Not a substitute for load balancer
    - - Based on user location and resource location
      - Can shift traffic to resources based on a bias that is allocated to location
      - Resources can be
        
        AWS resources (specify region)
        
        Non-AWS resources (specify lats & longs)
      - Must use Route53 Traffic Flow feature
    - - Based on client's IP
      - Provide a list of CIDRs & corresponding endpoints / locations
      - Use cases
        
        Optimize performance
        
        Reduce network costs
      - Example
        
        Specific ISP routed to specific location
- - - - ~15 Global health checkers checks endpoint
        
        Healthy threshold = 3 by default (about 18%)
        
        Interval = 30s by default (can set 10s at cost)
        
        Protocols
        
        HTTP
        
        HTTPS
        
        TCP
        
        Can choose locations
      - Pass = 2xx & 3xx response
      - Can use first 5120 bytes of response to pass / fail
      - Firewall must allow requests from Health Checkers
    - - Combine results of up to 256 other health checks
      - Can use OR, AND, NOT
      - Specify how many must pass
      - Use case
        
        Perform maintenance without causing all health checks to fail
    - - Useful for private resources
      - Health checkers are outside VPC, but can read CW alarms