aws_lb_listener cost estimation
A listener is free. It checks for connections on a port and forwards them, so the cost is the load balancer it belongs to, not the listener.
An aws_lb_listener attaches to an Application or Network Load Balancer and defines how to handle incoming connections on a given port and protocol, including TLS termination and routing rules. Listeners and their rules have no charge. You can add as many listeners and rules as your quotas allow without a per-listener fee.
The cost is entirely the parent load balancer. An ALB bills a fixed hourly charge plus Load Balancer Capacity Units (LCUs) that scale with new connections, active connections, processed bytes, and rule evaluations. An NLB bills hourly plus NLCUs. Adding a listener does not add a fixed cost, though a busier listener contributes to the capacity-unit charge through the traffic it accepts.
One real cost consideration for HTTPS listeners: TLS termination happens on the load balancer and is included in the LCU model, so there is no separate certificate-processing fee when you use an ACM certificate (ACM public certificates are free). The listener is where you attach that certificate, but it does not create a charge of its own.
c3x prices the load balancer and its capacity, and treats listeners and listener rules as free components of it.
Terraform example
A minimal but realistic configuration that C3X can estimate.
resource "aws_lb_listener" "https" {
load_balancer_arn = aws_lb.app.arn
port = 443
protocol = "HTTPS"
ssl_policy = "ELBSecurityPolicy-TLS13-1-2-2021-06"
certificate_arn = aws_acm_certificate.app.arn
default_action {
type = "forward"
target_group_arn = aws_lb_target_group.app.arn
}
}Pricing dimensions
What you actually pay for when you provision aws_lb_listener.
| Dimension | Unit | What's being charged |
|---|---|---|
| Listener and rules | free | Listeners, listener rules, and TLS termination config have no per-item charge. $0 |
| Load balancer | per hour + per LCU/NLCU | The parent ALB or NLB carries the real cost, scaling with traffic. ALB: ~$0.0225/hour + LCU |
Optimization tips
Common ways to reduce aws_lb_listener cost without changing the workload.
Route many services through one listener
One hourly balancer charge instead of manyUse listener rules with host and path conditions to serve multiple services from a single ALB and listener instead of running a balancer per service.
Use ACM certificates for free TLS
Attach an ACM public certificate to an HTTPS listener. ACM public certificates are free, and TLS termination is already included in the balancer's capacity charge.
FAQ
Does a load balancer listener cost extra?
No. Listeners and their rules are free. You pay only for the parent Application or Network Load Balancer, billed hourly plus capacity units that scale with traffic.
Is there a charge for HTTPS listeners or TLS termination?
No separate charge. TLS termination is included in the load balancer's capacity-unit pricing, and ACM public certificates are free. The listener is just where you attach the certificate.
How many listeners can I add before it costs more?
Adding listeners never adds a fixed fee. More traffic through them contributes to the load balancer's capacity-unit charge, but the listeners themselves stay free.
Related resources
Estimate this resource in your own Terraform
Free, open source, no API key. C3X parses your Terraform and shows line-item cost for every resource, including aws_lb_listener.