According to Logeshwaran, a dedicated Direct Connect port in US East (N.
Virginia) costs $219 a month at 1 Gbps, $1,642.50 at 10 Gbps, and $16,425 at 100 Gbps, a figure worth weighing for teams that, like those running automations through Activepieces, already move steady traffic between systems.
Before any data transfer, cross-connect or carrier circuit, actual monthly bills will be substantially higher.
Direct Connect is a dedicated private link between your site and AWS. Its traffic stays off the public internet, which matters when a data-residency or transfer-impact assessment says certain flows must not cross it.
Read the monthly column as the floor of the bill, not the bill.
Direct Connect pricing by port speed and type
| Connection | Port speed | Hourly rate (US East) | Monthly (730 hrs) | Transfer out | Included | Limits |
|---|---|---|---|---|---|---|
| Dedicated | 1 Gbps | $0.30 | $219 | $0.02/GB | Port, inbound data | One physical port, single-mode fiber |
| Dedicated | 10 Gbps | $2.25 | $1,642.50 | $0.02/GB | Port, inbound data | One physical port, single-mode fiber |
| Dedicated | 100 Gbps | $22.50 | $16,425 | $0.02/GB | Port, inbound data | One physical port, single-mode fiber |
| Hosted | 50 Mbps to 25 Gbps | Varies by partner and capacity | Varies | $0.02/GB | Partner-provisioned capacity | One virtual interface per connection |
Because dedicated ports are billed per hour, the monthly figures are simply the hourly rate times 730.
Dedicated connections: hourly port rates
Hourly, the 1 Gbps port is $0.30, the 10 Gbps port $2.25 and the 100 Gbps port $22.50. A full month of continuous hourly usage equals the fixed monthly rate.
Ten times the speed costs 7.5 times the price at the first step, then exactly ten times at the second.
At 400 Gbps the port reaches $62,050 a month, so the per-gigabit price keeps falling as you scale. Sizing up pays only if you'll actually fill the pipe.
Hosted connections through partners
Not every workload justifies a dedicated port, and a compliance archive syncing nightly is a good example. A hosted connection is capacity an AWS partner provisions on its own port, from 50 Mbps up to 25 Gbps.
Separating production from audit data means buying a second connection, because each hosted connection carries one virtual interface. The price depends on the partner, so quote it as part of the circuit.
Inbound data is free, and transfer out over Direct Connect is $0.02 per GB in US East. At 50 TB a month that's about $1,000, so egress is rarely the dominant line. It becomes one only at very high volumes.
Direct Connect free tier and what pricing includes
There's no free tier for Direct Connect ports. Once the port is up, the fee starts, so a proof of concept on a 1 Gbps port pays the full $0.30 an hour while it runs.

What the port fee includes is the AWS side only. The cross-connect and carrier circuit, which the following sections cost, are separate.
If you are running this arithmetic for your own team, see what the same workload costs on Activepieces.
Direct Connect costs at three sizes
Add AWS port fees to transfer out at the Direct Connect rate and you have each monthly bill. The cross-connect and carrier circuit sit on a separate non-AWS line that the AWS invoice never shows.

Treat that second line as part of the price, because it's the one you negotiate and the one that scales with redundancy.
Read it by comparing the last two rows against the subtotal: the gap between the internet row and the transfer row is your saving. The non-AWS line is what that saving has to cover.
Work each size the same way. Port fees are the hourly port rate times the hours in the month times the number of ports. Transfer is gigabytes out times the Direct Connect per-GB rate.
Small: one 1 Gbps link, 2 TB out
With a single port and modest volume, transfer is a small part of the AWS subtotal, and the carrier circuit and cross-connect can easily outweigh both AWS lines.
At this volume the per-GB saving over internet egress is thin, so the break-even depends almost entirely on your circuit quote.
If you're buying Direct Connect for cost alone here, check that quote first. It's more defensible as a choice for consistent latency or for keeping regulated traffic off the public internet.
Mid-size: redundant 10 Gbps pair, 50 TB out
Add redundancy and the port line changes first. Maximum resiliency doubles port fees, because you pay for a second set of ports in a separate location.
GDPR Article 32 expects resilience of processing systems, so for personal data this is often a requirement rather than an upgrade.
At this volume, transfer produces a real saving against internet rates, and the question is whether it covers two carrier circuits and two cross-connects. Price both paths, because the redundant design pays the non-AWS line twice.
At the large size, a redundant 100 Gbps pair with 500 TB out, the per-GB gap dominates. Volume carries the saving, and the port fees are modest next to the transfer bill you avoid.
The non-AWS line is still a separate commitment, usually multi-year, and it stays fixed if your traffic drops. Break-even here is a volume threshold, and the risk is falling below it after you've signed.
Hidden Direct Connect costs and limits teams hit
None of the charges around the second port appear on the AWS invoice. They're the cross-connect, the carrier circuit and the redundant path, so price the whole circuit rather than the port.
Costs that never appear on the AWS invoice
AWS sells the port. You buy everything between the port and your router elsewhere, and a finance review that stops at the AWS bill will undercount.
Article 32 of the GDPR requires security "appropriate to the risk", and Direct Connect traffic is private but not encrypted by default, so MACsec or an IPsec overlay is another cost to budget.
AWS sells the port. You buy everything between the port and your router elsewhere, and a finance review that stops at the AWS bill will undercount.
Five items fall outside the port price, or bite once the port exists, and the list below covers them. Treat each as a line in the circuit budget.
- The colocation cross-connect is a monthly fee set by the facility, not AWS, and charged for every link.
- The carrier circuit is a recurring fee from your provider, which usually dwarfs the port cost for long backhaul.
- A second link for resiliency doubles the cross-connect and circuit lines, ideally at a separate location.
- Transit Gateway fees are hourly attachment charges plus per-gigabyte processing.
- Port-hours are billed once the port is ready, even if unused.
If you want a shorter carrier line, look at location first. AWS has gone from 46 locations to over 60, then over 146, and now over 150.
A denser footprint means a facility near your data centre is more likely to exist. That shortens the carrier circuit you pay for.
Transit Gateway and inter-region charges
You may think of the traffic as cheap on the Direct Connect data-transfer rate, but it is also metered at the gateway, because Transit Gateway bills per attachment-hour and per gigabyte processed.
When traffic crosses regions, inter-region transfer is added. That matters for residency: if data must stay in one jurisdiction, a hub-and-spoke design can move it where it may not go, and it costs you to do so.
If the carrier install is delayed, you pay for a port that carries nothing. Port-hours start when the port is ready or 90 days after you request it, whichever comes first, so sequence the carrier order ahead of the AWS request.
Hit the route ceiling and the session drops. Each connection supports a fixed number of virtual interfaces, and each BGP session accepts a limited number of routes, 100 on a private virtual interface.
A large on-premises estate that can't summarise its prefixes will reach that limit. Summarise routes before ordering, or the redesign costs more than the port.
Worth checking against a plan that does not meter every step: one credit covers a whole run on Activepieces.
Direct Connect versus VPN and other networks
Until monthly transfer reaches somewhere between 1 TB and 20 TB, a Site-to-Site VPN is enough. Past that, Direct Connect's cheaper data transfer overtakes it, if you also need its bandwidth, latency or compliance posture. Run your numbers first.
Site-to-Site VPN as a cheaper Direct Connect alternative
According to Logeshwaran's comparison, the base fee is $36 a month for a VPN and $219 for a 1 Gbps Direct Connect port. That gap means the VPN is the cheaper choice while traffic is light.
At 1 TB out, the bill is $117 for the VPN against $239 for Direct Connect, so you're still ahead with the VPN, but by less each month.
At 20 TB out, the VPN reaches $1,827 and Direct Connect $619, which means Direct Connect is roughly one-third the cost.
Somewhere between those two volumes sits the crossover, and a team moving a few terabytes should measure its actual traffic before ordering a circuit.
You get IPsec encryption out of the box with the VPN, and setup in hours, not weeks. Its ceiling is 1.25 Gbps per tunnel, and it rides the public internet, so latency varies.
For regulated personal data that matters less than where the traffic terminates, which is a question of region choice, not link type.
Direct Connect partner and network-as-a-service options
Between the two sit partner and network-as-a-service routes. A partner supplies the carrier circuit and sometimes the cross-connect, so you avoid ordering both yourself, and provisioning is usually faster than a dedicated circuit.
You pay for that convenience in a margin on top of the port, and you still need to design redundancy, because one partner link is one failure domain.
Azure ExpressRoute and Google Cloud Interconnect compared
Azure ExpressRoute and Google Cloud Interconnect follow the same model as Direct Connect: a private circuit, a port charge and carrier costs you buy separately.
If you run more than one cloud, a single carrier-neutral facility can serve all of them, which spreads the circuit cost.
Answer each step below before the next, because that is the order in which these questions eliminate options.
- Check whether you need more than 1.25 Gbps per tunnel, as that's the per-tunnel bandwidth limit for Site-to-Site VPN. If so, a single VPN tunnel won't carry it.
- Check your latency tolerance. If the workload can't absorb internet jitter, a private circuit is justified.
- Check compliance requirements, including whether your auditor expects traffic to stay off the public internet.
- Price the full circuit: port, cross-connect, carrier and a second path for redundancy.
- If none of the first three applies, or the full circuit costs more than the benefit, fall back to the VPN.
What follows is how to price step four properly.
Monitoring Direct Connect spend with Activepieces
What the workflow can and can't do
Activepieces can watch a Direct Connect bill on a schedule, and its Free plan, with 1,000 credits a month and unlimited flows, covers that check, but it can't lower the bill.
The workflow reads cost from AWS Cost Explorer, compares it with a limit you choose, and tells someone when the circuit costs more than you planned. The saving comes from the audit you do first.
Auditing all Direct Connect circuit costs first
Start that audit by listing every line that belongs to the circuit, not just the AWS invoice. Port-hours and data transfer out appear on the bill.
The cross-connect fee from the colocation facility and the carrier circuit arrive on separate invoices, and the second connection you bought for redundancy shows up twice in each.
Write down which invoice carries each line and who approves it. Any line with no owner is the one that will surprise you, and AWS can't see it for you.
Routing Direct Connect cost alerts to team channels
The obvious tool is AWS Budgets, and it covers the basic version of what follows. It can alert on a cost threshold with no extra tooling.
Choose Activepieces when you want the alert to land in a channel your team already reads, or to log each month beside the non-AWS lines that Budgets can't see.
Its published pricing page lists 1 credit per flow run however many steps it has, where Zapier's pricing page bills per task and Make's bills per module, and the Free plan includes 1,000 credits a month with unlimited flows, so a monthly check with a router and a sheet insert costs one credit a run.
Below, a screenshot shows a ten-step flow in the Activepieces builder, titled "Test Flow".
It has a schedule trigger, a Google Sheets step, a loop, a date helper, an HTTP request, two AI steps, a Sheets insert, a router with a "Branch 1" and an "Otherwise" path, and a Gmail send-email step.
It is a different job from ours, but the shape is the one you need: a trigger, a fetch, a decision, then an action. Your version is shorter, and the router is the step that matters.
Stage 1: pull Direct Connect cost from the AWS bill
Set a schedule trigger to run monthly, or weekly if you want early warning. Add an HTTP request step that calls the Cost Explorer API, using credentials for a user permitted only to read cost data.
Filter the query to the Direct Connect service and group by usage type. Grouping matters because it separates port-hours from data transfer out, so you can see which one moved when the total does. A single total tells you that spend rose, not why.
Next, add a router. Branch 1 fires when the returned cost exceeds your limit; "Otherwise" handles the normal case.
Base the limit on the whole-circuit estimate from your audit, not on last month's AWS figure alone. A limit taken from the AWS invoice only will pass an overrun in any cost that sits on another invoice.
Sending Direct Connect alerts and logging monthly costs
On Branch 1, send an email or chat message naming the usage type that drove the overage.
On both branches, insert a row in a spreadsheet with the month, the AWS figure, and the carrier and cross-connect amounts you type in by hand.
After a few months that sheet is the whole-circuit cost, built from real invoices and ready to check against the original estimate.
Frequently asked questions
Is there a Direct Connect free tier?
No. AWS Direct Connect has no free tier. As of the 19 Nov 2026 check against AWS's Direct Connect pricing documentation, port-hours are billed from the moment a port is provisioned for you.
Nothing in the service is free to experiment with. Budget the port, the cross-connect and the carrier circuit as soon as you order, not once traffic flows.
Is data transfer in over Direct Connect free?
Yes. AWS doesn't charge for data sent into AWS over Direct Connect, so migrations and backup uploads cost nothing in transfer fees. Data transfer out is what you pay for, at a per-gigabyte rate that varies by the AWS Region you leave from.
If your workload mostly pulls data back to an on-premises site, model that direction, because it's the only one that drives the metered charge.
Is Direct Connect cheaper than a VPN at high volume?
Usually on transfer fees, not necessarily on the total bill. Site-to-Site VPN traffic leaving AWS is billed at standard internet transfer-out rates, while Direct Connect has a lower rate, so the gap widens with volume.
But Direct Connect adds fixed costs the VPN avoids: the port, the cross-connect and the carrier circuit.
Whether you break even depends on how much you send out each month against those fixed costs. Run both through the same whole-circuit sheet and compare the totals, not the per-gigabyte rates.
Can I cancel Direct Connect without a fee?
AWS doesn't impose a termination fee or long-term commitment on a dedicated port, but you can still be locked in elsewhere. Your colocation provider's cross-connect and your carrier's circuit usually carry their own contract terms, and a hosted connection follows the partner's agreement.
Read those contracts before you sign, since they're where an early exit costs money. Also delete the connection in AWS itself, because port charges continue until you do, even if the cable is already unplugged.

Do I need two Direct Connect connections?
If the link carries anything you can't lose, yes. A single connection is a single point of failure: one port, one cross-connect, one carrier path. AWS's resiliency guidance recommends redundant connections, and the most resilient designs place them at separate locations.
For personal data, Article 32 of the GDPR requires the ability to ensure ongoing availability and resilience of processing systems, so a one-cable design is hard to defend if an outage interrupts regulated processing.
The cost follows directly: price the second port, second cross-connect and second carrier circuit into the baseline, not as an optional extra.
A site-to-site VPN can serve as a cheaper fallback path, with the caveat that its performance will differ from the primary link when it takes over.
Related reading
References
Running the numbers
See what the same workload costs here.
Free forever plan, and every paid plan self-hosts at no extra cost.
See pricing Talk to sales

