Gateway Load Balancer Calculator

GLCUs = max(GB per hour ÷ 1, new flows per second ÷ 600); cost = endpoints × hours × endpoint rate + GB × per-GB rate + GLCUs × hours × GLCU rate. A Gateway Load Balancer inserts third-party inspection appliances into the path using GENEVE encapsulation on port 6081, and it bills in two places: the endpoint in the consumer VPC charges per hour and per GB, and the load balancer itself charges per GLCU-hour on the highest of its bytes and new-flow dimensions. Because traffic traverses the endpoint on the way to inspection and back, the per-GB endpoint charge is the component that grows fastest as inspected volume rises.

Inline inspection is often mandated by policy but rarely costed properly — at multi-gigabit volumes the endpoint data charge alone can exceed the appliance licences.

This calculator takes 7 inputs: Gateway Load Balancer endpoints, Traffic sent for inspection, New flows per second, Price per GLCU-hour, Price per endpoint-hour, Price per GB through an endpoint, Billable hours per month. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

For a resilient design, yes. Traffic from a zone should reach an endpoint in the same zone, both to survive a zone failure and to avoid cross-zone data transfer charges layered on top of the endpoint per-GB charge.

They are illustrative us-east-1 list prices. Gateway Load Balancer, endpoint hour and endpoint per-GB rates all vary by region and change over time, so confirm them on the Elastic Load Balancing and PrivateLink pricing pages before committing to a design.