Arkinu
AWS service comparison

Elastic Load Balancing (ELB) vs AWS Global Accelerator: differences and when to use each

Elastic Load Balancing (ELB)
AWS Global Accelerator

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Networking and Content Delivery

Elastic Load Balancing (ELB)

Automatically distributes incoming traffic across multiple targets, such as EC2 instances, containers, or IP addresses, in one or more Availability Zones, routing it only to healthy targets based on their health checks. It increases application availability and fault tolerance; it offers several types, such as Application Load Balancer, Network Load Balancer, and Gateway Load Balancer.

Exam phrases that point here

  • «distribute HTTP and HTTPS traffic across instances in multiple Availability Zones»

    An Application Load Balancer receives web requests and spreads them across the healthy targets in its target groups, which can be in several AZs.

    When not: If the traffic is TCP or UDP and calls for very low latency or static IP addresses, a Network Load Balancer fits. If users must be distributed across Regions, the load balancer is not enough: think of Amazon Route 53 or AWS Global Accelerator.

  • «route requests based on the URL path or host name»

    The listener rules of an Application Load Balancer can forward each request to a different target group depending on the path (/api/*) or the host (api.example.com).

    When not: A Network Load Balancer works at layer 4 and does not see HTTP paths or hosts. If the decision depends on the user's location or Region, the solution goes through Route 53 or Amazon CloudFront, not through the load balancer's rules.

  • «the load balancer needs static IP addresses or Elastic IP addresses»

    A Network Load Balancer provides one static IP address per Availability Zone and lets you assign Elastic IP addresses to it, something an Application Load Balancer does not have on its own.

    When not: If layer 7 features are also needed, you can put a Network Load Balancer in front of an Application Load Balancer. If the fixed IP addresses must be global and serve several Regions, AWS Global Accelerator fits.

  • «handle millions of requests per second with ultra-low latency over TCP or UDP»

    The Network Load Balancer is designed for large-scale layer 4 traffic with very low latency, and it preserves the client's source IP address.

    When not: If what matters is inspecting or routing HTTP content (paths, headers, redirects, authentication), the option is the Application Load Balancer even if the volume is high.

  • «transparently insert third-party virtual appliances, such as firewalls or intrusion detection systems»

    The Gateway Load Balancer distributes traffic across a fleet of virtual appliances and inserts them into the network path without the traffic being addressed to them.

    When not: If a third-party appliance is not required and an AWS-managed firewall is enough, AWS Network Firewall fits. To filter attacks on a web application (layer 7), AWS WAF.

  • «automatically replace instances that fail the load balancer's health checks»

    When the Auto Scaling group uses Elastic Load Balancing health checks, it replaces the instances that the load balancer marks as unhealthy.

    When not: By itself the load balancer only stops sending traffic to the unhealthy instance; the one that replaces it is Amazon EC2 Auto Scaling. Without enabling those health checks on the group, Auto Scaling only looks at the EC2 instance status.

Often paired with

  • Amazon EC2
  • Amazon EC2 Auto Scaling
  • Amazon Route 53
Study Elastic Load Balancing (ELB) →

Networking and Content Delivery

AWS Global Accelerator

Service that gives your application static anycast IP addresses and routes user traffic over the AWS global network to healthy endpoints in one or more Regions, such as load balancers or EC2 instances. It improves the performance and availability of applications with users around the world.

Exam phrases that point here

  • «static IP addresses that clients can add to their allow list»

    Each accelerator gets two static IP addresses that do not change even if endpoints are moved or added in other Regions, so clients configure them only once.

    When not: If a fixed IP address for a single resource in one Region is enough, an Elastic IP address may do. And if the content is HTTP and cacheable, CloudFront also offers anycast static IP addresses; the clue alone does not decide.

  • «UDP traffic for games or VoIP for users around the world»

    Global Accelerator supports TCP and UDP and carries traffic over the AWS global network from the nearest edge location, with lower latency and jitter than over the internet.

    When not: If the content is HTTP and can be cached (images, videos, downloads), the usual answer is Amazon CloudFront.

  • «fail over to another Region in seconds without depending on clients' DNS cache»

    Clients always use the same IP addresses; when an endpoint fails health checks, the accelerator sends new connections to another Region without waiting for DNS records to expire.

    When not: If DNS-based failover is acceptable, Amazon Route 53 with failover routing and health checks may be enough and simpler. And if the problem is the database, the solution is in the data layer (for example, cross-Region replicas), not in network traffic.

  • «send a percentage of traffic to another Region to test a new version»

    The traffic dial of each endpoint group and the weights of each endpoint let you split traffic between Regions or versions, useful for blue/green deployments or A/B tests.

    When not: If everything happens within a single Region, an ALB with weighted target groups solves it. If a DNS-based split is acceptable, Route 53 weighted routing also works.

  • «assign each player to a specific instance and port»

    A custom routing accelerator deterministically maps each accelerator port to an IP address and port on an EC2 instance, based on the application's logic.

    When not: If you only need to spread load across equivalent servers, you do not need custom routing: a standard accelerator or a load balancer is enough.

Often paired with

  • Elastic Load Balancing (ELB)
  • Amazon EC2
Study AWS Global Accelerator →