In a full-mesh scenario, every site in your any-to-any network can reach the cloud through a single, bandwidth-shaped connection. The cloud access is added as a separate logical service, so your existing full-mesh network keeps running with no changes to your on-premises routers.
When to use it
Use the full-mesh scenario when your network is already any-to-any - every site can talk to every other site - and one or more of those sites needs private access to a cloud. It is the most common starting point for enterprises that want broad cloud reach without singling out particular locations, and it scales naturally: sites added to the mesh later inherit cloud access without extra work.
How it works
A dedicated logical connection is created for your service over the shared cloud-facing port. One end is associated with your existing full-mesh network; the other with the cloud connection. Routing is exchanged between the two ends over BGP, so cloud routes are extended into your full mesh and your routes are advertised toward the cloud.
Bandwidth shaping is applied to the service so that traffic toward the cloud is held to the rate you ordered. Because this is a new logical connection rather than a change to your existing topology, the shaping and the cloud access are added without touching the routers your sites connect to - the full-mesh service continues to operate uninterrupted while cloud access is layered on.
Example Scenario
A national logistics operator runs around 40 regional depots on a full-mesh network where any site can reach any other. It rolls out a fleet-tracking application hosted in AWS, and every depot needs private, low-latency access to it. Rather than building links depot by depot, the operator adds a single bandwidth-shaped connection that extends AWS reachability into the existing full mesh. All 40 depots gain private access at once, none of the depot routers need reconfiguring, and as new depots join the mesh they pick up cloud access automatically.
Bandwidth planning
The cloud connection must be sized to carry the traffic your full-mesh service sends to it. Plan for the aggregate the mesh will generate, not a single site’s share.
For example, if the depots collectively need around 500 Mbps to AWS at peak, the AWS connection should be subscribed at 500 Mbps or above, and the full-mesh service shaped accordingly. If you later add a second scenario into the same AWS connection, its bandwidth needs to cover the combined total of both services - an individual service can only be shaped up to the headroom left within the cloud connection’s subscription.
What’s on the cloud side
The cloud connection at the far end is created in the cloud provider’s console. This page covers how full-mesh access is delivered on the Tata Communications side; for the cloud-side connection request and routing, see the relevant per-cloud section.