Dedicated Interconnect across clouds
A private circuit from your network into the cloud - Direct Connect, ExpressRoute, Cloud Interconnect, FastConnect - with BGP, a redundant pair, and the encryption question answered.
4 verified modules - all static-validated and publish-checked; live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | Direct Connect, and the Fact that It Is Not Encrypted | static-validated |
| Azure | An ExpressRoute Circuit with Peering and No Illusion of Encryption | static-validated |
| Google Cloud | Interconnect Attachments in a Pair, Encrypted by Decision | static-validated |
| Oracle Cloud | A FastConnect Circuit with BFD, a Partner, and a Gateway | static-validated |
How to choose
Start with the fact none of these encrypts by default: a private circuit is a private path through a colocation facility and a partner, not a private conversation. Then compare how each gets to a redundant pair, what the SLA needs, and whether the circuit can carry IPsec so the traffic is encrypted anyway.
When not to use
A circuit takes weeks to provision and bills whether or not routes cross it. If the requirement is encryption and predictable latency rather than dedicated bandwidth, a site-to-site VPN over the internet is up in an afternoon and the interconnect can be its future.