High severitycluster
Power BI Refresh Error:
AWS_RESOURCE_QUOTA_EXCEEDED
What does this error mean?
A Databricks cluster could not be launched because an AWS service quota was exceeded. Common limits include vCPU quotas per instance family, EC2 elastic network interfaces, or Elastic IP addresses.
Common causes
- 1The AWS account vCPU quota for the requested instance family (e.g., p3, r5) has been reached
- 2The maximum number of running EC2 instances in the region has been hit
- 3Elastic Network Interface (ENI) quota has been exhausted in the VPC
- 4A newly created AWS account has restrictive default quotas that were not pre-increased
- 5A large workload scale-up event consumed quota that other jobs expected to be available
How to fix it
- 1Open the AWS Service Quotas console and check the current usage vs. limit for the affected resource type
- 2Submit a quota increase request in the AWS Service Quotas console — this typically takes 24-72 hours
- 3In the interim, use alternative instance types that may have available quota (e.g., r5 instead of r4)
- 4Terminate unused EC2 instances or stop idle Databricks clusters to free quota
- 5Consider spreading workloads across multiple AWS regions to avoid per-region quota limits