Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Cloud-provider-specific limits and constraints when running e6data.
| Limit | Default | Adjustable |
|---|---|---|
| Concurrent EC2 instances per cluster | Limited by AWS account quotas | Yes - request quota increase |
| VPC peering for In-VPC deployments | Up to AWS default limits | Yes - request via support |
| S3 bucket access | Same-region recommended | Cross-region works but adds latency/cost |
| Cross-account IAM trust | Supported via role assumption | Standard AWS configuration |
| Limit | Default | Adjustable |
|---|---|---|
| Subscription quota for VM cores | Per Azure subscription default | Yes - request quota increase in Azure portal |
| ADLS Gen2 access | Same-region recommended | Cross-region works but adds latency/cost |
| Cross-tenant access | Supported via Managed Identity federation | Standard Azure configuration |
| Network Contributor on VNet | Required for In-VPC internal LB | Configured per cluster |
| Limit | Value | Notes |
|---|---|---|
| Max executors per cluster | 10,000 | Practical limit; most clusters are far smaller |
| Concurrent queries per workspace | Workspace-dependent | Contact support to raise |
| Result set size per query | 100 MB via REST API | Use streaming for larger |
| Catalog name length | 64 characters | Reasonable practical limit |
| Workspace name length | 1–18 characters | Hard limit |
