Skip to main content

Onboarding

A glimpse of what getting productive with CloudCADI looks like: deploying CloudCADI and connecting it to a customer cloud account.

1. First Deployment Walkthrough​

New engineers should complete one guided deployment before working independently. CloudCADI always deploys the same way - containers on Kubernetes, backed by PostgreSQL - only the managed services underneath change per platform:

  1. Pick a target platform from Deployment (AWS/Azure/GCP)
  2. Follow the platform-specific guide
  3. Once the deployment finishes, get the CloudCADI application URL from the deployment outputs and confirm it redirects to the CloudCADI login page

2. Connecting Customer Cloud Accounts​

Once CloudCADI itself is deployed, it still needs to be connected to whichever customer cloud accounts it will monitor/manage. This is a separate step from deployment, and the exact steps depend on both:

  1. Which cloud CloudCADI's backend is deployed on (AWS, Azure, or GCP)
  2. Which cloud the customer account being connected lives on (AWS, Azure, or GCP)

When both are the same cloud, CloudCADI connects using that cloud's native mechanism directly - for example a cross-account IAM role on AWS, or granting roles to CloudCADI's service account on GCP. When they differ, CloudCADI connects using OIDC-based workload identity federation between its own backend and the customer's cloud.

Pick the guide matching where CloudCADI is hosted, then the sub-page for the customer account you're connecting:

CloudCADI hosted on ↓ / Connecting account →AWSAzureGCP
AWSConnect AWSConnect AzureConnect GCP
AzureConnect AWSConnect AzureConnect GCP
GCPConnect AWSConnect AzureConnect GCP