AWS Elastic Load Balancing vs Google Cloud Load Balancing

AWS Elastic Load Balancing distributes incoming application traffic across targets and virtual appliances in one or more Availability Zones. It offers Application, Network, Gateway, and Classic Load Balancers, scales request handling with traffic, and runs configurable health checks on targets. Application Load Balancers support HTTP header-based routing, redirects, fixed responses, HTTP/2, and gRPC. Network Load Balancers support static Elastic IP addresses and AWS PrivateLink for TCP and TLS listeners. The service also supports SSL/TLS termination, certificate management, and client certificate authentication. CloudWatch metrics and logging are available for all four types. A single load balancer can distribute traffic across AWS and on-premises resources. Kubernetes support includes direct-to-pod routing for Application Load Balancers and private EKS clusters for Application and Network Load Balancers. AWS recommends different types for HTTP, transport protocols, third-party virtual appliances, and EC2-Classic applications. Usage charges vary by region; data transfer and public IPv4 address charges may be additional. New AWS customers receive a free tier for six months after account creation, with usage limits and up to $200 in credits.

Google Cloud Load Balancing has no write-up on Specifiction yet; its figures are above.