βοΈ Amazon Web Services (AWS)
What you'll learn
How to use S3 for artifact storage and SageMaker for execution β FlowyML abstracts away the complexity of Boto3 and AWS SDKs.
Deploy your FlowyML pipelines to the world's leading cloud provider with zero code changes.
Why AWS with FlowyML?
| Feature | Benefit |
|---|---|
| S3 Durability | 99.999999999% durability for model artifacts |
| SageMaker | Specialized ML instances (Trainium, Inferentia, GPUs) |
| IAM Security | Granular access control for data and resources |
| ECR | Private container registry for pipeline images |
πͺ£ S3 Artifact Store
Use Amazon S3 as the backend for all your pipeline artifacts:
π§ SageMaker Execution
Run your pipelines on Amazon SageMaker Processing Jobs or Training Jobs:
SageMaker Configuration
| Parameter | Type | Description |
|---|---|---|
role_arn |
str |
IAM role ARN for SageMaker execution |
instance_type |
str |
Compute instance (e.g., ml.m5.xlarge, ml.p3.2xlarge) |
region_name |
str |
AWS region |
instance_count |
int |
Number of instances (default: 1) |
volume_size_gb |
int |
EBS storage per instance (default: 30) |
π Authentication
FlowyML uses the standard AWS credential chain:
- Environment variables:
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY - Shared credentials file:
~/.aws/credentials - IAM Role: Automatic when running on EC2, Lambda, or SageMaker
Best Practices
Use IAM roles in production
Avoid hardcoding credentials. Use IAM roles on EC2/SageMaker for secure, credential-free authentication.
S3 lifecycle policies
Set up S3 lifecycle policies to automatically archive or delete old artifacts and reduce storage costs.