The selected-sites scenario gives cloud access to a chosen subset of sites on your existing network rather than to all of them. It uses the same modular, bandwidth-shaped connection as the other scenarios, so the sites you do not select are unaffected.
When to use it
Use selected sites when only specific locations should reach the cloud - a regional rollout, a pilot, or a compliance boundary that limits which sites may access a particular cloud workload. It lets you scope cloud access deliberately instead of opening it to the whole network, and it keeps that scope auditable.
How it works
A dedicated logical connection is created for your service and associated with the selected portion of your network at one end and the cloud connection at the other. The chosen sites are joined to a site-to-cloud association so that only their routes are extended toward the cloud and only they receive cloud routes in return; the remaining sites are not part of the exchange. Bandwidth shaping is applied so traffic toward the cloud is held to the ordered rate. As with the other scenarios, this is added without changes to your existing routers - both the selected and the non-selected sites continue to operate as before.
Example Scenario
A pharmaceutical firm has around 60 sites on its network, but only its three R&D laboratories are cleared to reach a regulated clinical-trial application hosted in Oracle Cloud. Using the selected-sites scenario, just those three labs receive private access to the application. The remaining 57 sites have no route to it at all, which keeps the regulatory boundary clean and auditable. Access is delivered as a single bandwidth-shaped service scoped to the chosen labs; if a fourth lab is later approved, it can be added to the same service without disturbing the rest.
Bandwidth planning
The cloud connection must be sized to carry the traffic of the selected sites. If you widen the selection later, or add another scenario into the same cloud connection, ensure the connection’s subscribed bandwidth covers the combined total - an individual service can be shaped only up to the headroom remaining within it.
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 access for the selected sites is delivered on the Tata Communications side; for the cloud-side connection request and routing, see the relevant per-cloud section.
Related pages