> For the complete documentation index, see [llms.txt](https://docs.brainboard.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brainboard.co/data/cloud-providers/supported-cloud-providers.md).

# Supported cloud providers

### Cloud provider definition

A **Terraform cloud provider** is a plugin that allows **Terraform** to interact with a specific cloud provider's API to create, manage, and delete resources. Each cloud provider has its own set of resources and data sources that can be used to define and manage infrastructure with **Terraform.**

You can use the provider block to specify which cloud provider you are using and configure its settings.

{% hint style="info" %}
This block is typically placed at the top of a **Terraform** configuration file, and you can specify multiple providers to manage resources across multiple cloud providers
{% endhint %}

<mark style="color:$primary;">**Brainboard**</mark> supports the following cloud providers:

### Azure (Azure Resource Manager)

<mark style="color:$primary;">**`AzureRM`**</mark> is the **Terraform** provider for **Azure Resource Manager (ARM)**, which is the service that allows you to **manage** Azure resources.

{% hint style="success" %}
It provides **Terraform** with the necessary API calls to interact with Azure's API and create, manage, and delete resources within your Azure account.
{% endhint %}

{% hint style="success" %}
When you use the **AzureRM** provider in **Terraform**, you can *<mark style="color:$primary;">define resources</mark>* such as *<mark style="color:blue;">virtual machines, storage accounts, and virtual networks</mark>*, and use **Terraform** to *<mark style="color:$primary;">create, update,</mark> and <mark style="color:$primary;">delete</mark>* those resources in **Azure.**
{% endhint %}

{% hint style="info" %}
Refer to the [credential page](/settings/integrations/cloud-providers/azure.md) to understand how to connect <mark style="color:$primary;">**Brainboard**</mark> with your Azure environments.
{% endhint %}

### AWS (Amazon Web Services)

The <mark style="color:$primary;">**`AWS`**</mark> provider for **Terraform** is a plugin that allows **Terraform** to interact with the **AWS API** to create, manage, and delete resources within an **AWS** account.

{% hint style="success" %}
It provides **Terraform** with the necessary API calls to *<mark style="color:$primary;">create, update,</mark> and <mark style="color:$primary;">delete</mark>* **AWS** resources such as *<mark style="color:blue;">EC2 instances, S3 buckets,</mark>* *and* *<mark style="color:blue;">RDS databases.</mark>*
{% endhint %}

{% hint style="info" %}
Refer to the [credential page](/settings/integrations/cloud-providers/aws.md) to understand how to connect <mark style="color:$primary;">**Brainboard**</mark> with your AWS environments.
{% endhint %}

### OCI (Oracle Cloud Infrastructure)

<mark style="color:$primary;">**`Oracle Cloud Infrastructure`**</mark> provider is a plugin that allows **Terraform** to interact with the **Oracle Cloud Infrastructure (OCI) API** to create, manage, and delete resources within an **OCI** account.

{% hint style="success" %}
It provides **Terraform** with the necessary **API calls** to *<mark style="color:$primary;">create, update,</mark> and <mark style="color:$primary;">delete</mark>* OCI resources such as *<mark style="color:blue;">Compute instances, Virtual Cloud Networks,</mark> and <mark style="color:blue;">Block Volumes.</mark>*&#x20;

It also allows managing other resources that are not directly related to **OCI**, such as *<mark style="color:blue;">DNS records</mark>* and others.
{% endhint %}

{% hint style="info" %}
Refer to the [credential page](/settings/integrations/cloud-providers/oci.md) to understand how to connect <mark style="color:$primary;">**Brainboard**</mark> with your OCI environments.
{% endhint %}

### GCP (Google Cloud Platform)

<mark style="color:$primary;">**`Google Cloud Platform`**</mark> provider for **Terraform** is a plugin that allows **Terraform** to interact with the **Google Cloud API** to  *<mark style="color:$primary;">create, manage,</mark> and <mark style="color:$primary;">delete</mark>* resources within a **GCP** project.

{% hint style="success" %}
It provides **Terraform** with the necessary **API calls** to *<mark style="color:$primary;">create, update,</mark> and <mark style="color:$primary;">delete</mark>* **GCP** resources such as **Compute Engine** **instances**, **Cloud Storage buckets**, and **Cloud SQL databases.**
{% endhint %}

{% hint style="info" %}
Refer to the [credential page](/settings/integrations/cloud-providers/gcp.md) to understand how to connect <mark style="color:$primary;">**Brainboard**</mark> with your **GCP** environments.
{% endhint %}

### Scaleway

<mark style="color:$primary;">**`Scaleway`**</mark> provider for **Terraform** is a plugin that allows **Terraform** to interact with the **Scaleway API** to *<mark style="color:$primary;">create, manage,</mark> and <mark style="color:$primary;">delete</mark>* resources within a **Scaleway** account.

{% hint style="success" %}
It provides **Terraform** with the necessary **API calls** to *<mark style="color:$primary;">create, update,</mark> and <mark style="color:$primary;">delete</mark>* **Scaleway** resources such as *<mark style="color:blue;">Compute instances, Volumes,</mark> and <mark style="color:blue;">Networks.</mark>*
{% endhint %}

### Providers versions

Every **Terraform** cloud provider has different versions for both its resources and data sources.

You can select any version from the list of versions:

<figure><img src="/files/pqkM15e9sBmrfwG5JMQO" alt=""><figcaption></figcaption></figure>

When you select a specific version, <mark style="color:$primary;">**Brainboard**</mark> loads all the resources of this version and the <mark style="color:$primary;">**Resource Configuration**</mark> panel of every resource will contain the parameters available in the selected version.

{% hint style="warning" %}
When selecting a different version, always do a <mark style="color:$primary;">**`plan`**</mark> to make sure that the code is valid, as most often parameters are updated between versions and some resources may be added or deleted
{% endhint %}