Practical guide
Why a low-traffic ALB still has a monthly cost
estimate fixed Application Load Balancer costs for small apps. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
Traffic is only one part of ALB cost
An Application Load Balancer accumulates running-hour charges while provisioned, even when its capacity usage is small. This makes the number of load balancers especially important for preview environments and small applications. Reducing requests alone leaves the time component largely unchanged.
Treat each environment as a separately justified resource. Production isolation, independent deployments, and security boundaries can be worth a higher fixed bill; a cost comparison should keep those requirements explicit.
Worked example: six small environments
Suppose six ALBs each run for a 730-hour planning month. Together they contribute 4,380 ALB-hours. Assume measured aggregate capacity usage is 300 LCU-hours across those environments.
If a technically valid design used two ALBs with the same aggregate capacity usage, running hours would fall to 1,460. The modeled change would be 2,920 × the ALB hourly rate. The 300 LCU-hours must remain an explicit assumption: changed routing rules and traffic behavior may alter it.
Use total fleet hours in the calculator’s load-balancer hours field. It represents summed resource hours, not a count of ALBs. Entering six rather than 4,380 would understate this example’s fixed component by a large amount.
Consolidation needs an application review
Before sharing an ALB, check listener configuration, certificates, routing rules, ownership, and failure impact. Combining environments can increase operational coupling and change rule-evaluation usage. A fixed-cost reduction does not prove the resulting design satisfies the same availability and security requirements.
Alternatively, review whether temporary environments need to remain provisioned between tests. Measure the real lifecycle rather than assuming every resource runs all month. Partial billing increments and provisioning behavior should come from the current AWS billing rules.
The calculator includes hourly and LCU components only. Public IPv4, transfer, application compute, and other services remain outside its subtotal. Keep those in a separate line-item comparison so a cheaper ALB number is not mistaken for a cheaper complete application.
Frequently asked questions
Will an empty ALB have a zero bill? Its running-hour component can still apply; verify all provisioned resources.
Can all applications safely share one ALB? That is an architecture decision. Compare the cost only after checking routing, certificates, isolation, ownership, and failure requirements.
Calculate your scenario
Use the application load balancer cost calculator. Keep the displayed region, pricing date, billing units, and exclusions alongside your result. The arithmetic examples above illustrate usage or explicitly hypothetical rates; they are not AWS quotes.
Source
Billing structure checked against official AWS documentation on September 6, 2026.