AWS Networking & Content Delivery

Elastic Load Balancing

Distributes incoming traffic across servers, containers and functions (Application, Network and Gateway load balancers).

What is Elastic Load Balancing?

Elastic Load Balancing spreads incoming traffic across healthy targets. Application Load Balancers route HTTP/HTTPS by path or host; Network Load Balancers handle very high TCP/UDP throughput; Gateway Load Balancers insert security appliances.

Key features

  • Health checks and automatic failover
  • HTTPS termination with ACM certificates
  • Path and host-based routing (ALB)
  • Static IPs and extreme throughput (NLB)
  • Integration with Auto Scaling and containers

What it is used for

  • High availability web apps
  • HTTPS termination
  • Blue/green deployments

When to use it

  • Any web application with more than one server
  • Zero-downtime deployments
  • Microservice routing

When something else fits better

  • A single small server where a load balancer adds cost without benefit

How pricing works

Charged per load-balancer hour plus capacity units based on connections, requests and bandwidth. Prices change and differ by region; we confirm current costs for your setup before you commit.

Equivalent on Google Cloud

The closest Google Cloud service is Cloud Load Balancing: global and regional load balancing behind a single IP address, with autoscaling backends.

How DomainHostly helps with Elastic Load Balancing

  • Plan: choose the right setup, size and region for your workload and budget.
  • Set up securely: configure Elastic Load Balancing with least-privilege access, encryption and backups where they apply.
  • Migrate: move from shared hosting, your own servers or the other cloud with minimal downtime.
  • Run and optimise: monitoring, updates and regular cost reviews so you only pay for what you use.

Networking & Content Delivery: Private networks, DNS, load balancing, CDN and connectivity between your sites and the cloud.

What to consider: Networking & Content Delivery

  • Plan IP ranges up front so networks can connect to your offices and each other later without overlaps.
  • Put databases and internal services in private subnets; expose only load balancers or CDNs publicly.
  • Watch data-transfer (egress) charges; a CDN often reduces both cost and latency.

Related services: Networking & Content Delivery