Skip to main content

Cloud Accounts

To get to the cloud accounts page, go to the left menu and click Cloud Accounts.

To add resources to Fleet Control, it is recommended that you onboard a cloud account and use the auto-discovery feature. At present, this feature is available for AWS and Azure and enables you to discover all virtual machines along with their tags and metadata.

By onboarding a cloud account, you can benefit from features such as:

  • Instance Discovery: There is no need to add your Virtual Machines manually as they will be automatically detected
  • Tag-based Selection: You can use tags to dynamically select resources to include in the operation plan
  • Start/Stop Action: You can use the built-in functionality to start or stop instances

1. Cloud Providers​

AWS​

To discover all of your EC2 instances, you need to onboard each AWS account by creating an IAM role and adding access configuration. To simplify this process, we have a CloudFormation template that is ready to use and will create all necessary parts and policies.

Add AWS Account

Azure​

To discover all your Azure Virtual Machines, you must onboard each subscription by creating a Service Principal and adding access configuration. You can utilize the onboarding bash script mentioned in the section below.

Add Azure Account

After onboarding your Azure Cloud Account, you must install an SSM Agent on every instance you want to use in Fleet Control. Instances with no SSM Agent will be discovered. However, you won't be able to execute any operation on it.

Install SSM Agent

2. List of Accounts​

By default, Cloud Accounts are sorted by Account Name, but you can also sort them by Date Added, Date Updated, Status, and Cloud Provider.

Additionally, you can Delete cloud accounts from this section.

3. Account Status​

Next to each cloud account name, you will see an icon that shows one of three connection statuses:

  • Connected: This means your cloud account is connected, and everything is working as expected
  • Access Missing: This means that we cannot find the credentials for the account in our internal service
  • Access Error: This status means that either the login credentials are invalid, expired or the regions specified by you are not accessible
  • In progress: This status means that scanning process is in progress