On June 15, 2026, AWS did something the game-hosting world had been asking for: it made network bandwidth free on Amazon GameLift Servers — for every instance from generation 6 onward, on-demand and spot, no commitment, applied automatically.
Credit where it’s due. For years, egress was the line on a GameLift invoice nobody could predict — bandwidth out of AWS billed per gigabyte, scaling directly with how successful your game got. AWS’s own example: a 1,000-CCU shooter on c6g instances that used to cost ~$4,485 in compute plus $1,507 in bandwidth now costs $2,978 — a 34% drop, with the bandwidth line gone. That’s a real improvement, and it kills the most unpredictable variable in multiplayer cost planning.
So if you read an older comparison — including older versions of ours — claiming “GameLift’s egress line is bigger than the entire competing bill,” that’s no longer true for modern GameLift fleets. Good.
Now here’s the part most of the coverage skipped.
The catch: “free” is tied to GameLift, not plain EC2
Read AWS’s wording carefully: bandwidth is free “for all Amazon GameLift Servers instances, generation 6 or newer.” The benefit is scoped to GameLift’s own instances — the all-in-one product that bundles GameLift compute with FleetIQ autoscaling and FlexMatch matchmaking.
It does not apply to plain EC2.
And “all-in-one” doesn’t mean hands-off: you still write the scaling rules and push your deployments yourself through the AWS console and FleetIQ. What’s now free is the bandwidth on those GameLift instances.
If you run your own dedicated game servers on EC2 — which is exactly what a lot of studios do — you’re still paying standard AWS data transfer at ~$0.09/GB, and that line still scales with every player. That’s the common setup when:
- Pragma Engine allocates your servers (Gameye is an official Capacity Provider there)
- Nakama drives hosting through its Fleet Manager
- a custom matchmaker / backend calls EC2 directly
- you run Agones on EKS and orchestrate it yourself
None of those get the free-bandwidth benefit, because none of them run on GameLift’s instances. They’re you, on EC2, paying egress like always.
What changed and what didn’t
| AWS GameLift (gen-6+) | EC2 Self-Hosted | |
|---|---|---|
| Backend | FlexMatch / FleetIQ | Pragma, Nakama, Agones, etc. |
| Outbound bandwidth | Free (since June 2026) | ~$0.09/GB, unchanged |
| Who runs the fleet | You (autoscaling via FleetIQ) | You |
| Server SDK | GameLift Server SDK | Whatever you wire up |
| Egress scales with players | No longer | Yes — the success tax |
| China | Excluded — egress applies | Egress applies |
So “is GameLift egress free in 2026?” has an annoying-but-honest answer: it depends what you’re running. GameLift’s own instances? Yes, on gen-6+. Your own servers on EC2? No.
Why this trips people up
The phrase “AWS dropped egress for game servers” is spreading, and it’s quietly wrong. AWS didn’t drop EC2 egress — it folded bandwidth into GameLift’s own instance pricing, which it can do because it controls that product end to end. The underlying EC2 data-transfer rate is exactly what it was.
For a studio choosing how to host, that distinction is the whole decision. If you run on AWS GameLift — its instances, its Server SDK, FleetIQ, FlexMatch, the AWS-only footprint — you get free bandwidth (you still own the scaling rules and deploys). If you keep control of your stack on your own EC2 with the backend you already run, you keep the egress bill too. “Free bandwidth” isn’t a property of AWS; it’s a property of running on GameLift’s instances specifically.
The free bandwidth is a lock-in, not a gift
Look at what you have to do to keep it. Free egress applies only while you stay fully inside AWS — GameLift’s managed hosting, its Server SDK in your binary, its AWS-only footprint. Stay in that box and bandwidth is free. Want flexibility anywhere, and it comes straight back:
- A different backend — Pragma, Nakama, Agones, or a custom matchmaker that allocates your own servers? Those run your fleet on EC2, not GameLift’s managed instances, so standard EC2 egress (~$0.09/GB) returns.
- Multi-cloud or your own bare metal? Not on the table — GameLift is AWS-only.
So AWS didn’t make bandwidth free; it made bandwidth free inside its walled garden. The discount is payment for maximum commitment to the AWS ecosystem — their hosting, their SDK, their matchmaker, their cloud. The moment you want a say in your backend or infrastructure, the egress bill is back.
That’s the whole case for an independent orchestrator. Gameye includes bandwidth on every provider and region and leaves your backend open — native Pragma and Nakama, FlexMatch in standalone, or any HTTP matchmaker, across 21 providers plus bare metal. You get the cost savings without the handcuffs. And against Edgegap — the other managed option studios weigh — egress is billed per-GB regardless. Of the three, only Gameye gives you both included bandwidth and full backend flexibility: cheaper than pure AWS the moment you want any choice, cheaper than Edgegap on bandwidth, period.
The cost lever moved — it didn’t disappear
Here’s the bigger shift. With bandwidth off the table for GameLift fleets, the comparison that actually decides your bill is no longer egress — it’s the processor.
A game server tick is mostly single-threaded, so clock speed sets how many players fit on a core. GameLift’s mainstream instances run 2.8–3.9 GHz virtual cores (and on c7i a “vCPU” is half a physical core). Higher-clock dedicated silicon does meaningfully more game-server work per core, so the honest metric stopped being cost per vCPU and became cost per concurrent player at your tick rate. That’s the comparison we walk through in full in Gameye vs AWS GameLift, and you can model it for your own load in the cost calculator.
And for the self-host crowd still paying EC2 egress: that’s exactly where an orchestrator that includes bandwidth on every provider and region changes the math — while keeping your existing backend. Gameye integrates natively with Pragma and the matchmakers you already use and with Nakama, so you’re not trading your stack for a bandwidth discount.
The short version
- AWS made bandwidth free on AWS GameLift gen-6+ instances — a real, welcome change.
- It’s not EC2-wide. Self-host on EC2 (Pragma, Nakama, Agones, custom) and you still pay ~$0.09/GB.
- “Is GameLift egress free?” → yes on GameLift’s own instances, no for your own servers on EC2.
- With bandwidth settled for GameLift fleets, the cost question moved to per-core performance and cost per player — not gigabytes.
If you’re on AWS GameLift and happy there, enjoy the lower bill. If you’re self-hosting on EC2 to keep control, the egress line never left — and that’s worth knowing before you assume the headline applies to you.
Running your own servers on AWS and want to see what dropping the egress line actually looks like? Model your load in the calculator or start a free trial — no sales call required.