Cloud Integrations

​

What are Cloud Integrations?

​

How Integrations Work

• Integrations belong to your organization, not individual workspaces
• One integration can be shared across multiple workspaces
• Centralized credential management with distributed usage

Organization: "ML Startup"
├── Integration: "AWS Production Account"
│   ├── Used by: "Model Training" workspace
│   ├── Used by: "API Deployment" workspace
│   └── Used by: "Analytics" workspace
└── Integration: "GCP Development Account"
    ├── Used by: "Development" workspace
    └── Used by: "Experiments" workspace

​

Supported Providers

​

Amazon Web Services (AWS)

• Authentication: IAM roles or access keys
• Resources: EKS clusters, EC2 instances, S3 storage, Secrets Manager
• Features: Multi-account support, cross-region deployments

​

Google Cloud Platform (GCP)

• Authentication: Service account JSON keys
• Resources: GKE clusters, Compute Engine, Cloud Storage, Secret Manager
• Features: Workload identity, project-based organization

​

Microsoft Azure

• Status: Coming soon
• Planned: AKS clusters, Virtual Machines, Blob Storage, Key Vault

​

Integration Features

• Real-time status monitoring
• Automatic credential validation
• Connection testing and diagnostics
• Smart retry mechanisms

• Environment tagging (dev/staging/prod)
• Multi-region support
• Cost tracking and allocation
• Resource lifecycle management

​

Common Integration Patterns

​

Single Account Pattern

Small Team Setup:
└── AWS Integration: "Company Account"
    ├── Workspace: "Web App"
    ├── Workspace: "Mobile API"
    └── Workspace: "Analytics"

​

Environment Separation

Enterprise Setup:
├── AWS Integration: "Development Account"
│   └── Dev/staging workspaces
└── AWS Integration: "Production Account"
    └── Production workspaces only

​

Multi-Cloud Strategy

Advanced Setup:
├── AWS Integration: "Primary Workloads"
├── GCP Integration: "ML & Analytics"
└── Azure Integration: "Legacy Systems"