Skip to main content

Resource onboarding without a cloud account

Fleet Control allows the onboarding of virtual machines from cloud accounts that were not added to the Fleet Control. It supports resources from cloud providers, such as AWS, Azure, Google Cloud, and IBM Cloud. Our system explicitly supports and recognizes these providers. Additionally, the system accommodates resources from other cloud providers and on-premise machines, categorizing these as OTHER. This approach broadens the scope of resource integration, ensuring comprehensive coverage of cloud and on-premise environments.

Caveats​

It is important to emphasize that resources without their associated cloud account onboarded may lack support for certain functionalities. We do not support the following functionalities:

Unsupported functionalities
Start Virtual Machine & Stop Virtual Machine system actions: This is currently unsupported for resources added without their cloud account for following providers: Google Cloud, IBM Cloud, OTHER.
Google Cloud labels: These labels are unsupported for resources added without their cloud account. See Resource labels for more information.
IBM Cloud tags: These tags are unsupported for resources added without their cloud account. See Tags for more information.

Onboarding process​

In most cases, the onboarding process follows the same procedure as onboarding virtual machines in Hybrid mode.

Prerequisites for IBM Cloud resources​

  • Metadata service: The metadata service must be enabled. See Enabling the metadata service for more information.

  • Secure metadata service access: Only secured access to the metadata service is supported to ensure maximum security. See IBM secure metadata access for more information.

  • Windows resource configuration: Additional configuration steps are necessary when onboarding a resource with a Windows system. See IBM metadata Windows configuration for more information.