Multi-Cloud Connectivity – the easiest way to do it

16 - July 2019
By Stephan Scholz

There is a huge demand for automated Cloud setup …. (what goes here?)

With Cloud adoption on the rise, Multi-Cloud Connectivity is one of the most critical services for most large enterprises today. Computing and storage resources in different VPCs (virtual private Clouds) from different public Cloud providers and the enterprise’s own private Cloud are usually connected via IP (Layer 3). The enterprise IT team is looking for the best way to manage and control the complex combination of clouds.

The expectations of the IT team are that any new Cloud configuration be an automated process, and should not require any specific learning curve for each system. The reality is that the process to configure the underlying data network infrastructure to accommodate a new cloud system, is often far from being automated – especially if some public or long distance network domains are involved. When the cloud service is spread over several cities or even countries, there is a need for manual configuration which requires specific networking knowledge. This is not only takes too long but is also very error prone. Therefore, a new virtual SDN-based approach is required in order to fully automate the process.

This new SDN-based approach, is currently in field trial by a service provider in a multinational network, and is based on the following two building blocks:

  • Enterprise Self-Service – this block enables the enterprise to fully automate the process of Multi-Cloud connectivity based on its specific network infrastructure. This service meets the enterprise’s need for an automated higher layer application that establishes Cloud service in just a few minutes.
  • Multi-Cloud connectivity services – This block gives the cloud service provider full visibility of the entire cloud services (missing a word here – environment?) sold to the different enterprises using standard cloud applications such as SBI (South Bound Interface). Such applications can be used to enforce the respective configuration (e.g. L3-VPN or E-LAN connections) for example, within the underlying network.

The first item covers all enterprise application-specific requirements that are very precisely defined with all cloud-applications.

The second item is focused on the service provider, and is where Atrinet’s NetACE changes the game: Identify underlying network structure and resources

NetACE discovery capabilities make it possible to locate all of the elements available in the network and the services that that work with these elements. Through this very quick, automated process users can explore in detail the exact, real time status of the network including devices, resources, services etc.

Design Multi-Cloud connectivity service in minutes

The NetACE unique Model Editor plays a critical role in the ability to build a multi-cloud connectivity service in minutes. Without any adaptation code, the system can design the required service regardless of which network devices the underlaying L2/3-network consists. This capability makes it possible to design services with critical settings and resources including flexible parameters.  This becomes even more important in cases where the Model Editor is designing all services based on network real time status (from previous discovery).

Automate the process

Once all the respective Multi-Cloud connectivity services are designed, Enterprise Self-Service can be used to activate the service. The main usage is to setup the correct network connections and services and activate them. When service is no longer required, a respective delete command can automatically remove all related network configurations and services.

With automation, it is becoming much easier to achieve multi-cloud connectivity as it can be easily implemented with the know-how that most IT teams already have.


Feel free to contact us, request a demo or a free trial – more information can be found on Atrinet’s website (

Leave a Reply

Your email address will not be published. Required fields are marked *