A Cloud Gateway privately links your CubePath VPC to AWS, Google Cloud or Azure over a dedicated interconnect — never the public internet. Start from the Cloud Gateway page in my.cubepath.com.

Why a private interconnect

Compared with a VPN over the public internet, a dedicated circuit gives you:

  • Predictable latency and throughput, because the traffic doesn't share a path with the rest of the internet.
  • No egress over the public internet, which matters both for compliance and, often, for the other cloud's bandwidth bill.
  • BGP routing on both ends, so the two networks exchange prefixes rather than you maintaining static tunnels.

It's the right answer for hybrid workloads: a database on CubePath baremetal feeding an application in AWS, a migration in progress, or a workload split across providers on purpose.

Deploy

  1. 1
    Contact Sales
    From the Cloud Gateway page, click Contact Sales to open a request and tell us about your workloads.
  2. 2
    Scope the link
    On a discovery call we pick the cloud provider service — AWS Direct Connect, Cloud Interconnect (GCP) or ExpressRoute (Azure) — plus regions, bandwidth and redundancy.
  3. 3
    We provision it
    CubePath sets up the dedicated layer-2 circuit, the cloud-side service and BGP peering on both ends. Private interconnects typically take 5 to 15 business days.
  4. 4
    Attach and announce
    Connect your existing VPC / VNet and announce your prefixes over BGP. Traffic stays on the private link end to end.

Plan around the lead time

Five to fifteen business days is physical provisioning at both ends, and it isn't something that can be rushed at the last minute. If the interconnect is on the critical path of a migration or a launch, start the conversation while the rest of the design is still moving.

Worth having ready for the discovery call: which cloud and region, the prefixes each side will announce, your expected sustained bandwidth, and whether you need redundant circuits.

What it doesn't do

  • It isn't a VPN. There's no self-service tunnel to configure; it's a provisioned circuit.
  • It doesn't route between your prefixes for you. Both ends announce over BGP, and the routing policy is yours to define.