6 documented AWS ELB cost inefficiencies, each with how to detect it and how to fix it.
AWS ELBCER-0187
An ELB with only one registered EC2 instance does not achieve its core purpose-distributing traffic across multiple backends. In this configuration, the ELB adds complexity and cost without improving availability, scalability, or fault...
AWS ELBCER-0059
Classic Load Balancers that no longer serve active workloads will persist if they are not properly decommissioned. This often happens after application migrations, architecture changes, or testing activities. Even if no connections or...
AWS ELBCER-0006
Network Load Balancers that are no longer needed often persist after architecture changes, service decommissioning, or migration projects. When no active TCP connections or traffic flow through the NLB, it still generates hourly...
AWS ELBCER-0003
Application Load Balancers that no longer serve active workloads may persist after application migrations, architecture changes, or testing activities. When no incoming requests are processed through the ALB, it continues to generate the...
AWS ELBCER-0062
Gateway Load Balancers that no longer have active traffic flows can continue to exist indefinitely unless proactively decommissioned. This often happens after network topology changes, security architecture updates, or environment...
AWS ELBCER-0359
A single Application Load Balancer can route traffic for many applications using listener rules on host names and URL paths, forwarding each to its own target group. In practice many organizations give every microservice, environment or...
