Connect cloud accounts on CloudBolt Documentation

Connect AWS

Mon, 01 Jan 0001 00:00:00 +0000

This guide explains how to configure AWS connections in the CloudBolt Platform to support billing functions.

You can deploy the required AWS resources as part of this connection, or connect a stack you already deployed separately (see Configure AWS accounts).

Each AWS management (billing) account requires its own connection. A single connection covers the member accounts in that organization.

Prerequisites

A CloudBolt Platform user with the Operations or Admin role. Refer to Manage roles.
The AWS account prerequisites described in Configure AWS accounts.

Connect a new AWS account

Use this option if you haven’t deployed the CloudBolt CloudFormation template. This flow opens CloudFormation in a new browser tab using your current AWS Console session, so make sure you’re signed in to the AWS Console for the account you’re connecting before you start.

Connect Azure

Mon, 01 Jan 0001 00:00:00 +0000

The process is automated: you authorize CloudBolt and select the subscriptions to include, and CloudBolt handles the rest.

Before you begin

Ensure you have completed the steps in Configure Azure tenants.

There are three stages to the onboarding process:

Authorize: Sign in to your Azure tenant and grant CloudBolt read-only consent
Configure: Select which subscriptions and billing scope to include
Provision: CloudBolt creates the required Azure resources and begins importing your cost data

The active part of this process takes approximately 10 minutes, after which time historical data import, if enabled, continues in the background.

Connect GCP

Mon, 01 Jan 0001 00:00:00 +0000

Connect your Google Cloud Platform (GCP) environment to the CloudBolt Platform to enable cost analysis, resource inventory, and optimization recommendations across your GCP projects.

CloudBolt offers two connection methods:

OAuth connect (recommended): Sign in with Google to let CloudBolt automatically discover and provision resources.
Setup script (manual): Generate a Terraform or gcloud script to run in your own environment for full control.

Both methods create a Workload Identity Federation (WIF) credential that CloudBolt uses for ongoing, passwordless data collection.