Managing the Cloud Account's Space Settings

As Colony admin, when associating a cloud account to a space, you can do the following:

• Associate the cloud account to spaces to allow members of those spaces to use the cloud accounts in their deployments.
• Set sandboxes to be public or private
• Decide how to deploy sandboxes in the space (creating a dedicated cloud network per sandbox or using an existing network)

In this article:

• Viewing a cloud account’s settings
• Associating a cloud account to another space
• Defining the cloud account’s network settings in the space
• Deleting/resetting cloud account settings in the space

Viewing a cloud account’s settings

To view a cloud account's settings:

1. Open the Administration page and click the Cloud Accounts tab.
2. Click the cloud account’s more actions menu and select Edit.
   The cloud account’s space settings page is displayed.
   • The cloud account’s name is displayed at the top left corner with a tooltip listing the cloud account’s ID, and authentication details:
     
   • Compute Services lists the different compute services associated with this cloud account. A compute service can be an Azure or AWS cloud account and any associated Kubernetes compute services residing on the cloud provider.
   • Spaces lists the spaces the selected compute service is associated to.
   • Network Settings displays the cloud account’s network settings in a specific space.

Associating a cloud account to another space

To associate a cloud account to a space:

1. Open the Administration page and click the Cloud Accounts tab.
2. Click the cloud account.
3. Click the compute service and the “+” button next to the Spaces column heading.
   
4. From the drop-down menu, select the appropriate space.
   The new space association is added to the Spaces list, displaying the network settings area to the right.

Defining the cloud account’s network settings in the space

The network settings are defined on the space level. In other words, the same cloud account can have different network settings in different spaces.

NOTES: This section only applies to sandbox environments as networking in production environments is defined in the blueprint YAML’s infrastructure section. Also, you cannot modify AWS network settings, which are internet facing by design.

Defining the network settings

This section only applies to Azure sandboxes. 

To define the network settings:

1. Open the Administration page and click the Cloud Accounts tab.
2. Click the cloud account.
3. Click the appropriate space.
   The Network Settings area is displayed to the right.
4. Leave the Expose sandboxes to the Internet checkbox selected if you want the cloud account to deploy public (internet facing) environments in this space.
5. In the Sandbox deployment networking environments section, you can choose what type of infrastructure to deploy for new environments. Colony supports two types:
   • Dedicated, which is the default, means that Colony deploys a new Azure cloud infrastructure, including the virtual networks, subnets, security groups, and additional details for each sandbox environment and deletes this entire infrastructure when the sandbox ends.
   • In Shared mode, sandbox environments use an existing virtual network and subnets in an Azure cloud region. For example, you could have the sandbox deploy on a predefined VNET dedicated to your dev/test activities and connected via VPN to your on-premise network. Shared mode is only available on Azure. Shared mode only applies to Azure sandbox environments.

Defining an existing virtual network for sandbox environment deployments (Shared mode)

To define an existing virtual network:

1. Open the Administration page and click the Cloud Accounts tab.
2. Click the cloud account.
3. Select the cloud account and click the suitable space tile.
4. Make sure Expose sandboxes to the Internet is unselected.
5. Click Shared.
6. Click + Add Network.
   The Virtual Network Setup dialog box is displayed.
   
7. Provide the following details:
   • Region: Azure region that contains the desired VNET and subnets. Sandboxes will be deployed in this infrastructure.
   • Virtual Network: Azure VNET name in the format <RESOURCE-GROUP>/<VNET-NAME>. For example: company-rg/internal-network-1.
   • Gateway subnet: Name of the subnet that will contain the Azure Application Gateway resource that routs traffic to the relevant applications in the sandbox.
     • The gateway subnet cannot be defined as the application or management subnet when using this cloud account in this space.
     • A subnet can be defined as a gateway subnet only if it is empty or associated to gateway applications.
   • Management subnet: Name of the subnet that will contain the sidecar and QualiY machines.
   • Applications subnet: Name of the subnet that will contain the sandbox applications. Click the + Add Subnet button to specify additional application subnets.
8. Click Confirm.
9. Repeat to add additional VNETs.
10. Click Apply to save your changes.

Deleting/resetting cloud account settings in the space

Deleting the cloud account's space association

To delete the cloud account’s space association:

1. Open the Administration page and click the Cloud Accounts tab.
2. Click the cloud account.
3. Click the remove button on the space tile.
   For example:
   
   A window pops up, prompting you to confirm the action.
4. Click Confirm.

Deleting a virtual network setup

To delete a virtual network setup:

1. Open the Administration page and click the Cloud Accounts tab.
2. Click the cloud account.
3. Select the space.
4. In the Network Settings area, click the Virtual Network you wish to delete
   The Virtual Network Setup dialog box is displayed.
5. Click Delete in the bottom left corner.

Resetting a cloud account's network settings in the space

To reset a cloud account’s network settings in the space:

1. Open the Administration page and click the Cloud Accounts tab.
2. Click the cloud account.
3. Select the space.
4. In the Network Settings area, click the Reset button in the bottom left corner.