Onboarding

A glimpse of what getting productive with CloudCADI looks like — from zero to a working deployment.

1. Access & Accounts

• Get added to your organization's OIDC identity provider group for CloudCADI (Entra ID / Okta / Auth0 / etc.) — this is the only login CloudCADI uses, there's no separate password
• Confirm you can sign in to the CloudCADI UI via SSO
• Join the relevant Slack/Teams channel where deployment and alert notifications land

2. Environment Setup

git clone https://github.com/your-org/CloudCADI.git
cd CloudCADI
npm install
cp .env.example .env
docker compose up -d postgres   # local PostgreSQL for development
npm run dev

Local development points OIDC_ISSUER_URL at a dev/test tenant on your identity provider — production and staging environments point at the same provider, just a different client/tenant.

3. 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 in a sandbox/dev cluster
3. Confirm kubectl get pods shows everything Running/Ready and /healthz responds
4. Sign in through your IdP to confirm the OIDC flow is wired up end to end
5. Pair with a teammate to review

4. 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 — because it relies on identity federation (WIF / federated credentials) between CloudCADI's own backend and the customer's cloud — 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)

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

CloudCADI hosted on ↓ / Connecting account →	AWS	Azure	GCP
AWS	Connect AWS	Connect Azure	Connect GCP
Azure	Connect AWS	Connect Azure	Connect GCP
GCP	Connect AWS	Connect Azure	Connect GCP

All 9 pages are placeholder content

Every page behind this table is dummy/draft content scaffolded to match the shape of the real steps — replace with validated procedures per combination before publishing externally.

5. Key Resources

Resource	Link
Architecture overview	What is CloudCADI?
Deployment guides	Deployment
Connecting customer accounts	Onboarding § 4
Integration docs (Slack, Teams, Jira, ServiceNow, Enterprise AI, Azure Fabric)	Integration
Support channel	Placeholder

6. Checklist Before Going Live

• Read the architecture overview
• Completed a sandbox deployment on Kubernetes with a real PostgreSQL connection
• Confirmed OIDC sign-in works against the target environment's identity provider
• Connected at least one customer cloud account end-to-end using the guide matching your hosting cloud
• Understand rollback procedure for your target platform (helm rollback)

note

This is intentionally a glimpse, not the full internal runbook — expand each section with your team's actual access request process, support channel names, and go-live sign-off steps.