Skip to main content

Tutorial: Create Multiple Overlay Networks

Abstract

The multi-WPC feature of CloudConnexa allows the Owner to set up multiple WPCs using the same account. Each WPC can then be dedicated to a specific use case or department in order to isolate and segment the networks from each other completely.

Overview

Owen is in charge of IT and Networking for his company. They have been using CloudConnexa for access to AWS for a few years now. Owen got a request from Amy (Director of R&D) to provide connectivity to some applications and services they are developing on Azure. Amy wants to pay for the connectivity using a special projects budget and use Azure AD for authentication as opposed to Okta, which all employees use because it is a prerequisite for the projects they are working on.

As many of Amy's requirements require global configuration changes to the existing Wide-area Private Cloud (WPC) used for AWS access, Owen cannot just add the Azure Network to it. That leaves Owen with two choices: Sign up for a new CloudConnexa account with a different email address or Create another WPC using the existing account.

Owen decided to create a new WPC in the existing account because of the following:

  • He won't need to set up a new account with a different email address and monitor multiple email inboxes for CloudConnexa notifications.

  • He can switch quickly between the multiple WPCs he is administrating without needing to log in and log out.

  • All WPCs are visible in one place.

  • While in the same account, he can pay for and increase/decrease the users in each WPC independently.

Setup

  1. Owen clicks on Cloud ID displayed on the left navigation panel.

  2. The panel expands to the right with Add Cloud ID shown at the bottom, which Owen clicks.

  3. He purchases a subscription for the new WPC using Amy's corporate credit card.

  4. He adds a new WPC to that subscription by providing a Cloud ID for it.

  5. He is taken to the administration portal of the new WPC, where he proceeds to:

    1. Configure SAML authentication with Azure Active Directory.

    2. Add a Network and deploy a Connector on the Azure VNet.

    3. Configure Applications for the private network.

    4. Configure Access Groups to those applications.

  6. To switch back to the original WPC, Owen again clicks on Cloud ID displayed on the left navigation panel and clicks on the Cloud ID of the WPC from the list shown in the expanded panel to the right.

In this section: