> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudeval.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported clouds and IaC formats

> Check which cloud providers and infrastructure formats Cloudeval supports today.

These docs focus on the workflows customers can use today.

<Warning>
  Cloudeval is Azure-first for live cloud sync. AWS CloudFormation beta supports static JSON/YAML IaC topology and evaluation, not live AWS connections or full Azure report parity. Terraform coverage is narrower still.
</Warning>

## Current support status

| Workflow                                   | Status              | Notes                                                                                                                                                                      |
| ------------------------------------------ | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Azure Cloud sync connection                | Available           | The main supported live-cloud path today.                                                                                                                                  |
| Azure subscription discovery               | Available           | Supported for Azure service principal connections.                                                                                                                         |
| Azure resource group discovery and scoping | Available           | Optional scoping is available during connection setup.                                                                                                                     |
| Single ARM template import                 | Available           | Supported through file upload or template URL.                                                                                                                             |
| Multi-file ARM workspace import            | Available           | Supported with `.cloudeval/config.yaml` for visualization source and linked-template resolution.                                                                           |
| Bicep-generated ARM JSON review            | Available           | Compile Bicep to ARM JSON, then import the generated template.                                                                                                             |
| AWS CloudFormation evaluation              | Limited beta        | Static JSON/YAML IaC topology and evaluation can use reviewed AWS beta controls, cfn-lint deployment-quality checks, and Checkov additional IaC findings where applicable. |
| Terraform IaC findings                     | Limited             | Checkov can produce additional IaC findings for supported Terraform workflows. This is not live-cloud sync or full Well-Architected parity.                                |
| AWS live environment connection            | Not available today | AWS live sync is not a production-supported workflow today.                                                                                                                |
| GCP live environment connection            | Not available today | GCP is not a supported workflow today.                                                                                                                                     |
| Kubernetes, Pulumi, or telemetry evidence  | Planned             | Treat as roadmap direction until documented as available.                                                                                                                  |
| Multi-cloud parity                         | Planned             | Do not assume Azure workflows map 1:1 to other providers.                                                                                                                  |

## Provider and format matrix

| Provider | Format or source         | Current treatment                           |
| -------- | ------------------------ | ------------------------------------------- |
| Azure    | Live cloud sync          | Available                                   |
| Azure    | ARM JSON                 | Available                                   |
| Azure    | Bicep-generated ARM JSON | Available                                   |
| Azure    | Terraform                | Limited IaC findings                        |
| AWS      | CloudFormation JSON/YAML | Limited beta static topology and evaluation |
| AWS      | Terraform                | Limited IaC findings                        |
| AWS      | Live cloud sync          | Not available today                         |
| GCP      | Live cloud sync or IaC   | Not available today                         |

## What this means in practice

* Use **Azure Cloud sync** when you need live cloud inventory and current Azure evidence.
* Use **ARM or Bicep-generated ARM JSON** as the supported Azure IaC baseline.
* Use **AWS CloudFormation beta** for static JSON/YAML IaC topology and evaluation, not as an end-to-end AWS Well-Architected assessment or live AWS connection.
* Treat **Terraform** output as additional IaC findings unless a workflow states a broader reviewed treatment.
* Expect unsupported provider, format, resource, or policy areas to appear as `Not assessed`.

## Why the docs are strict here

Evaluation claims need clear boundaries. Cloudeval now covers more IaC evidence than the older Azure-only docs described, but that does not make every provider path equal. The docs separate live cloud sync, static IaC evaluation, beta controls, and additional IaC findings so teams can plan without guessing.

## Next step

If you want a Cloud sync path, start with [Connect an Azure environment](/guides/connect/azure). If you want an IaC path, go to [Import an ARM or Bicep template](/guides/connect/arm-bicep). For count and attribution details, read [Evaluation methodology and attribution](/trust/evaluation-methodology).