SkaleData DocsConnect a cloud
Give SkaleData a deployer role in your AWS, GCP, or Azure account with the skale CLI, and verify the connection.
SkaleData deploys infrastructure inside your cloud account. The skale CLI handles the entire setup — it detects your active cloud session, creates the deployer role, verifies the connection, and registers it with SkaleData.
Before you begin
Install the CLI and sign in with skale auth login. Then check that
your account has room for a cluster; see Cloud quotas.
Connect your cloud
Prerequisites
- An AWS account with admin access
- AWS CLI installed and authenticated — the setup command runs against your active AWS session, so you must be logged in first:
# SSO-based auth
aws sso login
# Or configure with access keys
aws configureImportant: The person running skale clouds setup must have an active, authenticated AWS CLI session with permissions to create IAM roles and policies. This is typically an account administrator.
Run setup
skale clouds setup --provider awsThe CLI will:
- Detect your AWS account ID and region from the active CLI session
- Create the
SkaleDataDeployerIAM role - Verify that SkaleData can assume the role
- Register the cloud connection
Cloud connected! AWS — 123456789012 (verified)
Next step:
skale clusters create --cloud <cloud-id>What gets created
An IAM role (SkaleDataDeployer) with the following managed policies:
| Policy | Purpose |
|---|---|
AmazonEC2FullAccess | VPC, subnets, security groups, instances |
AmazonS3FullAccess | DAG storage buckets |
AmazonEC2ContainerRegistryFullAccess | Container image registry |
IAMFullAccess | Create per-app IAM roles (IRSA) |
CloudWatchFullAccess | Monitoring and logging |
AmazonSSMReadOnlyAccess | Parameter store lookups |
Plus an inline policy for:
| Permission | Purpose |
|---|---|
eks:* | EKS cluster lifecycle |
route53:* | DNS records for data plane routing |
kms:* | Encryption key management |
elasticloadbalancing:* | Load balancers for ingress |
No long-lived credentials are stored. SkaleData uses OIDC federation to assume the role with short-lived tokens.
Default configuration
| Setting | Value |
|---|---|
| Cluster type | EKS |
| Default node size | m5.xlarge (4 vCPU, 16 GB) |
| Node autoscaling | 1–5 nodes |
| DAG storage | S3 bucket |
Useful commands
# List connected clouds
skale clouds list
# Re-verify a connection
skale clouds verify <cloud-id>To create a cluster on the connected cloud, follow the Quickstart.