A deployment scenario describes how your existing network reaches the cloud - which sites get access, and how traffic is shaped. IZO™+ Multi Cloud Connect supports four: full mesh, hub-and-spoke, cloud-to-cloud, and selected sites. They share one modular foundation, so you can add or change a scenario without disturbing your existing services.
The modular foundation
Every scenario is delivered on the same underlying design. For each service, a dedicated logical connection is created over a shared, high-capacity cloud-facing port; one end is associated with your network, the other with the cloud connection. Routing is exchanged between the two ends over BGP, and bandwidth is shaped per service to the rate you order.
The practical consequence matters more than the mechanics: because each service is added as its own logical connection, turning on cloud access - or changing which sites reach the cloud - does not require changes to your existing on-premises routers, and your current services keep running uninterrupted. This is what lets you start with one scenario and layer on others later.
The four scenarios
|
Scenario |
Who reaches the cloud |
Typical use |
Use Case |
|
Full mesh |
All sites in an any-to-any network |
Broad cloud access across the estate |
A logistics firm gives all 40 depots access to a fleet app in AWS |
|
Hub-and-spoke |
Access mediated by a hub |
Networks that centralize traffic through a hub |
A bank routes 200 branches to Azure through its head-office hub |
|
Cloud-to-cloud |
Two clouds reach each other |
Inter-cloud traffic kept off the internet |
A media firm links AWS storage to Google Cloud analytics privately |
|
Selected sites |
A chosen subset of sites |
Scoping access to specific locations |
A pharma firm gives only 3 of 60 sites access to a regulated app |
How to choose
Work from your existing network shape and who needs cloud access:
-
If your network is any-to-any and many sites may need the cloud --> full mesh.
-
If you already concentrate traffic through a hub, or want the cloud itself to be the central point all sites reach --> hub-and-spoke.
-
If the requirement is to connect two clouds to each other rather than sites to a cloud --> cloud-to-cloud.
-
If only specific locations should reach the cloud - a pilot, a regional rollout, or a compliance boundary --> selected sites.
You are not locked to one choice. Because each service is a separate, independently shaped logical connection, you can combine scenarios - full mesh for the core and selected sites for a regulated subset, for instance - and adjust them over time.
A scenario decides which sites reach the cloud; the service model - IZO™+ Multi Cloud Connect Direct or Flex - decides how those sites reach the backbone. The two are chosen independently.
Each scenario can be delivered single-path or with diverse dual paths (Standard, High or Maximum resiliency)
A note on bandwidth
Each scenario’s connection is shaped to the bandwidth you order, and the cloud-side connection must be sized to carry the combined traffic of every service pointed at it. If you run more than one scenario into the same cloud connection, plan that connection’s bandwidth to cover their aggregate - an individual service can only be shaped up to the headroom remaining within the cloud connection’s subscription. See Bandwidth Tiers and Slabs.