Cloud Providers

A Cloud Provider allows integration of services such as GCP, Azure, or AWS into the platform. It is associated with Cloud Templates that define the characteristics of the virtual machines (VMs) to be deployed.

This way, Reemo can automatically create VMs on demand directly from its interface, without using the cloud provider’s console, and then link these VMs as workstations for users.

Note

When a Cloud Provider is created in Reemo, it is disabled by default and must be explicitly enabled by an instance administrator.

Overview

The list of Cloud Providers displays:

• Name: identifier chosen by the administrator.

• Type: provider (e.g., GCP, AWS, Azure).

• Managed By: responsible administrator.

• Visibility: Public or Private.

• State: Enabled or Disabled.

List of Cloud Providers

Creating a Cloud Provider

1. Click New Provider.

2. Fill in the fields:

   • Name: provider name.

   • Type: select GCP, Azure, or AWS.

   • Visibility: Public or Private.

   • Comments: administrative notes.

3. Specific parameters:

   • Maximum VMs: limit of deployable VMs for this provider.

Creating a Cloud Provider

GCP Configuration Example

For GCP, a service account configuration is required. You must provide:

• Project ID: GCP project identifier.

• Service account client email: service account email address.

• Service account private key: associated private key.

Configuring a GCP Cloud Provider

Cloud Provider Profile

Each Cloud Provider has a profile page with:

• General information: type, creation date, visibility, state, VM limits.

• Configuration: entered parameters (e.g., API keys, project ID).

• Computers: virtual machines deployed via this provider.

• Actions: edit or delete.

Cloud Provider Profile

Integration with Cloud Templates

Each Cloud Template is linked to a type of Cloud Provider. Examples:

• A GCP template can only deploy on a GCP Cloud Provider.

• An AWS template can only apply to an AWS Cloud Provider.

Templates define:

• VM size.

• Operating system.

• Network and storage options.

Thus, when creating a workstation:

1. The administrator selects an appropriate template.

2. The platform deploys the VM on the associated Cloud Provider.

3. The VM is automatically integrated into Reemo and linked to a user.

Private Cloud Providers Association

A Cloud Provider can be defined as either Public or Private:

• Public: automatically accessible by all organizations.

• Private: must be explicitly associated with the organizations that need to use it.

This distinction allows opening certain environments to everyone (Public) or restricting cloud resources only to certain organizations (Private).

Managing Associations

From the Cloud Providers section of an organization, it is possible to associate an existing Private Cloud Provider on the platform.

List of Cloud Providers associated with an organization

Adding a Private Cloud Provider

To associate a Private Cloud Provider with an organization:

1. Click New provider then Assign existing provider.

2. Choose the desired provider from the list.

3. Save the association.

Window for associating a Private Cloud Provider

It is also possible to directly create a new cloud provider from the organization context.

Menu for creating a Cloud Provider from an organization

Summary

The Cloud Providers module allows you to:

• Integrate GCP, Azure, or AWS into the platform.

• Centralize access configuration via service accounts.

• Automatically deploy VMs using Cloud Templates.

• Avoid switching back and forth between Reemo and cloud consoles.

• Public Cloud Providers are visible to all organizations.

• Private Cloud Providers require explicit association.

This speeds up the provisioning of workstations and simplifies their management.