How Integrations Work
Integrations are optional extensions that add new flavors of stack components to ZenML. When you install an integration, you get:- Stack Components: Orchestrators, artifact stores, experiment trackers, etc.
- Service Connectors: Authentication and resource management for cloud platforms
- Materializers: Custom serialization for integration-specific data types
- Step Operators: Execute individual steps on specialized infrastructure
Installation
Install integrations using thezenml[integration-name] syntax:
Available Integrations
AWS
Amazon Web Services integration with SageMaker, S3, and ECR
Google Cloud
GCP integration with Vertex AI, GCS, and GCR
Azure
Microsoft Azure with AzureML and Blob Storage
Kubernetes
Native Kubernetes orchestration and deployment
Kubeflow
Kubeflow Pipelines orchestration
MLflow
MLflow experiment tracking and model registry
W&B
Weights & Biases experiment tracking
SageMaker
AWS SageMaker orchestration and step operators
Vertex AI
GCP Vertex AI pipelines and training
Integration Categories
Cloud Platform Integrations
Provide comprehensive support for major cloud providers:- AWS: S3 artifact storage, ECR container registry, SageMaker orchestration
- GCP: GCS artifact storage, GCR container registry, Vertex AI orchestration
- Azure: Blob Storage, AzureML orchestration and training
Orchestrator Integrations
Execute pipelines on specialized orchestration platforms:- Kubernetes: Native k8s orchestration with full Pod customization
- Kubeflow: Kubeflow Pipelines (KFP) v2 orchestration
- SageMaker: AWS SageMaker Pipelines with distributed training
- Vertex AI: GCP Vertex AI Pipelines with AutoML support
Experiment Tracking Integrations
Track experiments and compare runs:- MLflow: Open-source experiment tracking with model registry
- Weights & Biases: Cloud-based tracking with collaboration features
Stack Components by Integration
Each integration provides different types of stack components:| Integration | Orchestrator | Artifact Store | Container Registry | Experiment Tracker | Step Operator |
|---|---|---|---|---|---|
| AWS | ✓ | - | ✓ | - | ✓ |
| GCP | ✓ | ✓ | - | ✓ | ✓ |
| Azure | ✓ | ✓ | - | - | ✓ |
| Kubernetes | ✓ | - | - | - | ✓ |
| Kubeflow | ✓ | - | - | - | - |
| MLflow | - | - | - | ✓ | - |
| W&B | - | - | - | ✓ | - |
Service Connectors
Most cloud integrations include service connectors for authentication:Using Integration Components
After installing an integration, register its components with your stack:Integration Settings
Many integrations support step-level settings for fine-grained control:Best Practices
Install Only What You Need
Install Only What You Need
Integration dependencies can be large. Only install integrations you actively use to keep your environment lean:
Use Service Connectors
Use Service Connectors
Service connectors provide centralized credential management and automatic authentication:
- Store credentials once, use across multiple components
- Support multiple authentication methods (keys, roles, service accounts)
- Automatic credential refresh for cloud platforms
- Audit trails for credential usage
Separate Dev and Prod Stacks
Separate Dev and Prod Stacks
Use different stacks for development and production:
Version Lock in Production
Version Lock in Production
Pin integration versions in production environments:
Next Steps
Cloud Integrations
Learn about AWS, GCP, and Azure integrations
Orchestrators
Explore orchestration options
Experiment Tracking
Track and compare experiments
Service Connectors
Set up authentication
