Please enable JavaScript.

Coggle requires JavaScript to display documents.

Route 53 (Global accelerator (feature (assign an anycast IP to your client…

- - - - Same source IP will route to same endpoint
      - this is for video ingestion
        
        where it have audio, video multiple stream in 1 session
- - - - can response 8 healthy A records or lesser
        
        Means 8 IP address will be return when query the DNS
        
        3type if health check
        
        http/https
        
        TCP
        
        http/https with specific string
      - Ex: example.com with 8 diff IP and diff TTL
      - can support health check at route 53
        
        so only return heathty A record
        
        Simple routing policy can't do health check
        
        If all unhealthy, will respond up to 8 unhealthy IP
        
        Not sutable for ELB
        
        Ex: if have 4 Ec2 web server, will respond all 4
        
        if 2 unhealty, only respond with 2 healthy Ec2 IP
        
        If not configure health check, will assume is health for the IP
      - weight
        
        Distribute traffic base on weight of the A record
        
        Ex: 2 ELB A record was created . 1 with weight 7 and the other with weight 3 . ELB1 will serve 70% of trafic. ELB2 will serve 30 %
    - - Based on the gegraphic location of the Original IP queries
      - Ex: 2 A record created. 1 ELB at SG, Another 1 at USA. if the IP is located at SG, will route to SG region ELB.If IP is from US, will route to ELB located at US-east1
      - Means on the IP address of the DNS queries
      - If route 53 can't decide the location of IP, will route to default record. If there is no default record, it will return no answer
        
        Exa,m[; : IP from United kingdom will go to default record
    - - Based on physical distance of ELB and use
      - Draw a diagram, US-East and US west,
      - If user nearer to east, route to east
      - Let say hve 2 ELB, US-East and US-west
    - - can specify multiple value
      - but not multiple record
      - route 53 respond queries randomly
      - can't support health check from Route 53
        
        can configure A record point to ELB
        
        Coz ELB has health check
    - - based on distance from user to location of your resources.
      - Based on lattitude and longtitude
- - - - when someone browse your DNS, the name server will tell where to find your S3 or Web server
    - - Type
      - Value
      - Name of the record which correspond to the domain name which you to route to