☀️
Dev7Days
  • 😄Welcome
  • Local Setup
    • ⚙️Setup Terminal
    • ⚙️Setup IDE
    • ⚙️Setup Neovim
  • Rust
    • 🦀Cargo
  • Java
    • 🍃Spring Boot
      • Spring Boot Annotaion
      • Spring Boot Learning
    • 🍃JDK vs JRE vs JVM
    • 🍃What is JDBC ?
    • 🍃What is Data Source in Java ?
    • 🍃Check vs Unchecked Exception
    • 🍃What is Servlet in Java ?
    • 🍃Filter vs Interceptor
    • 🍃Mockito
    • 🍃Maven CLI
    • 🍃Maven Archetype
  • Go
    • 🔹Go Routine and Channel
    • 🔹Go CLI
  • Ruby and Rails
    • ♦️Ruby Syntax
    • ♦️Rails Framework
    • ♦️Rails Structure
  • Fundamental
    • 📚Git Command
    • 📚Interpreter vs Compiler
    • 📚DTO vs DAO
    • 📚Http Status
    • 📚What is Batch Process ?
    • 📚Https
    • 📚Local Storage vs Session Storage vs Cookies
    • 📚Authentication & Authorization
    • 📚Database Index
    • 📚What is GRPC ?
    • 📚What is Microservice ?
  • Database
    • 🗃️What is Transaction ?
    • 🗃️ACID
  • Postgres
    • 🐘SELECT
    • 🐘Column Alias
    • 🐘Order By
    • 🐘SELECT DISTINCT
  • Elastic Search
    • 🔍What is Elastic Search ?
    • 🔍Node and Cluster
  • Kubernetes
    • ☸️What is Kubernetes ?
    • ☸️Kubernetes Architecture
      • Node
      • ETCD
      • Kube API Server
      • Controller Manager
      • Kube Scheduler
      • Kubelet
      • Kube Proxy
  • ☸️Pod
  • ☸️ReplicaSet
  • ☸️Deployment
  • ☸️Service
  • ☸️Config Map
  • ☸️Namespaces
  • ☸️Kube Apply Command
  • ☸️Scheduling
    • Manual Scheduling
    • Labels and Selectors
    • Taints and Tolerations
    • Node Selector
    • Node Affinity
    • Resource Requirements and Limits
    • DaemonSets
    • Static Pods
    • MultipleSchedulers
  • ☸️Monitoring
  • AWS
    • 🔸How can users access AWS ?
    • 🔸IAM
    • 🔸EC2
      • User Data
      • Instance Types
      • Security Group
      • Purchasing Options
      • Placement Groups
      • Elastic Network Interface (ENI)
      • EC2 Hibernate
      • EC2 Storage
    • 🔸ELB & ASG
      • Health Checks
      • Target Group
      • ELB Types
      • Sticky Sessions
      • Cross Zone Load Balancing
      • Load Balancer - SSL and SNI
      • Deregistration Delay
      • ASG
    • 🔸RDS & Aurora DB
      • RDS
        • Storage Auto Scaling
        • Read Replica
        • Multi AZ
        • RDS Custom
        • Backup
        • RDS Proxy
      • AWS Aurora
        • Read Replica
        • Endpoint and Auto Scaling
        • Aurora Serverless
        • Global Database
        • Machine Learning
        • Backup
        • Database Cloning
      • RDS & Aurora Restore options
      • RDS & Aurora Security
    • 🔸Elastic Cache
    • 🔸Route 53
      • Records
      • Hosted Zones
      • Health Check
      • Routing Policies
  • Backend Security
    • 🎩SQL Injection
    • 🎩Cross site script (XSS)
    • 🎩Cross site request forgery (CSRF)
    • 🎩Man in the Middle (MITM)
    • 🎩Insecure Direct Object Reference (IDOR)
    • 🎩Distributed denial of service (DDOS)
  • Medium
    • 👨‍💻Gamer to Coder
    • 🐳Docker
      • Docker #1
      • Docker #2
    • 💊DI and IOC
    • ☸️Kubernetes
  • Book
    • 📚System Design Interview - An Insider's Guide (Volume 1
Powered by GitBook
On this page
  • (1) Simple
  • (2) Weighted
  • (3) Failover
  • (4) Latency Based
  • (5) Geolocation
  • (6) Multi Value
  • (7) Geoproximity
  1. AWS
  2. Route 53

Routing Policies

PreviousHealth CheckNextSQL Injection

Last updated 12 months ago

Routing Policies define how Route 53 respond to DNS queries.

There are 7 type of policies

  1. Simple

  2. Weighted

  3. Failover

  4. Latency based

  5. Geolocation

  6. Multi Value Answer

  7. Geoproximity

(1) Simple

It will respond only single resource. We can specify multiple values in same record but client will choose only one random value from these and If we use Alias then it will choose only one AWS resource. This policy does not support for health check.

(2) Weighted

In this strategy we will apply weighted to each of destination so the traffic will go to destination that has a highest weighted . Weighted is similar to the number of traffic in percentage units. Also It can be associated with Health Checks feature.

Usecase

  • Load balancing between region

Good To Know:

  • Asign a weightof 0 to a record to stop sending traffic to a resource

  • If all records have weight of 0, then all records will be returned equality.

(3) Failover

It will has 2 kind of record we need to set one for primary instance and another for secondary instance. When Primary instance is failed then it will return Secondary instead. This strategy require to have Health Check.

(4) Latency Based

It redirects to the resource that has the least latency close to user. Latency is based on traffic between users and AWS region.

e.g : Germany users may be directed to the US (If that is the lowest latency). Also It can be associated with Health Checks feature.

(5) Geolocation

This routing is baed on user location and If it did not find the location of user , then it will return default record instead (No match on location). Also It can be associated with Health Checks feature.

If you use the VPN, your location is based on that VPN.

Usecase

  • Restrict content on location

  • Website localization

(6) Multi Value

It will return multiple resources. Also It can be associated with Health Checks feature.

(7) Geoproximity

In the same location we have mutiple resource there but we will set the bias to one of these resources then the traffic mostly go to that resoruce.

🔸
Drawing
Drawing
Drawing