MCMMCMBy Revdau
Why MCM
v1.1 is unreleased — see v1.0 for the current stable release.

Accounts & Supported Providers

How MCM connects to cloud and infrastructure providers, and which providers are supported.

Accounts & Supported Providers

An account in MCM is a credential-backed connection to a cloud provider, source control system, container registry, or host. Connecting an account is a one-time step — every MCM module (Discovery, FinOps, Governance, SecOps, Orchestration, and Observability) then uses that connection without any per-module credential setup.


Connecting an Account

MCM provides a guided onboarding wizard for each provider type, with permission templates and step-by-step validation. Each connected account shows a live connection status — Active, Warning, or Failed — so credential issues are visible before they cause module outages. Accounts can be labelled with environment tags (Production, Staging, Development) that carry through to all modules.


Supported Providers

Cloud Providers

ProviderCredential TypeModules Unlocked
AWS AWSIAM Role (cross-account assumed role)Discovery, FinOps, Governance, SecOps, Orchestration, Observability
Azure AzureService Principal (App Registration + client secret)Discovery, FinOps, Governance, SecOps, Orchestration, Observability

Source Control

ProviderCredential TypeModules Unlocked
GitHub GitHubPersonal Access Token or GitHub AppDiscovery (repos, orgs), SecOps (code scanning)

Container Providers

ProviderCredential TypeModules Unlocked
Docker Hub Docker HubUsername + Access TokenDiscovery (images), SecOps (container scanning)
Docker Docker (self-hosted)Docker socket or daemon APIDiscovery (containers), SecOps (container scanning)

Host Providers

ProviderCredential TypeModules Unlocked
Ubuntu UbuntuSSH key or agent-based (Wazuh agent)Discovery (hosts), Governance (host policies), SecOps (host scanning), Observability (host logs & metrics)

On this page