{
  "id": 3787089,
  "title": "The LCU Trap: Why Your Load Balancer Bill Has Nothing To Do With Bandwidth",
  "url": "https://urgent.news/2026/08/27/the-lcu-trap-why-your-load-balancer-bill-has-nothing-to-do-with",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-27T18:01:24.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/christopher123/the-lcu-trap-why-your-load-balancer-bill-has-nothing-to-do-with-bandwidth-3ich"
  },
  "original_language": "en",
  "account": "Many engineers mistakenly believe that load balancer costs scale linearly with throughput. They expect to pay directly based on the amount of data being transferred. However, this is not how Amazon's ALB (Application Load Balancer) or NLB (Network Load Balancer) are charged. Instead, AWS bills by Load Balancer Capacity Units (LCU). The rate is determined by the single largest dimension among four factors evaluated hourly: new connections/flows per second, active connections/flows, bandwidth (in Gbps), and rule evaluations per second (only for ALB, beyond 10 free rules).\n\nThe key rule governing billing is that customers are charged for the maximum of these dimensions, not the sum. You pay for the highest demand, regardless of how other factors compare. This means optimizing the other metrics has no impact on your bill.\n\nTo illustrate the difference, consider two scenarios:\n\n1. A high-connection workload:\n- ALB requires 2,000 LCU for 50,000 new connections per second, costing around $11,712 per month.\n- NLB requires only 63 LCU for the same volume, costing approximately $308 per month – a 32 times better efficiency.\n\n2. Rule evaluation costs:\n- Every rule beyond the first 10 incurs additional LCU cost calculated as (rules - 10) * rps / 1,000.\n- With 5,000 requests per second and 50 path-based routing rules, rule evaluations alone require 200 LCU, amounting to $1,168 per month, despite negligible bandwidth usage.\n\nCustomers can use an interactive calculator on jslet.com to input their specific traffic profile and see which dimension is binding them – the single factor determining their actual cost.",
  "summary": "` Most engineers assume load balancer costs scale with throughput: \"We push 2 Gbps, so our bill should reflect 2 Gbps.\" That intuition is wrong. AWS doesn't bill ALB or NLB by throughput. They bill by LCU (Load Balancer Capacity Units) —and you pay for the single largest dimension , not the sum. The Rule: Pay for the Max, Not the Sum Four dimensions are evaluated every hour: New connections/flows…",
  "key_points": [
    "Load balancer costs based on Load Balancer Capacity Units (LCU), not bandwidth.",
    "Optimizing non-LCU factors has no impact on load balancer bill."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}