- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2024 08:22 AM
Hey folks,
I have been trying to set up an SQL warehouse for Databricks in AWS (on a new account) but I keep getting this:
Cluster Start-up Delayed. Please wait while we continue to try and start the cluster. No action is required from you.
This kept happening the whole day, no matter the type of warehouse (tried Serverles and PRO) and no matter the size. Any clues?
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2024 11:45 AM
Hi @suela ,
How are you doing today?
It sounds like your cluster startup delay could be due to a few common issues. First, double-check your AWS VPC and security group settings to ensure they allow the necessary connections. Also, make sure your account isn’t hitting any EC2 instance quotas, and verify that your IAM roles have the correct permissions. Sometimes, new AWS accounts can have configuration hiccups, so if the problem persists, it might be worth reaching out to Databricks support for a deeper dive. Hope this helps!
Regards,
Brahma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2024 11:45 AM
Hi @suela ,
How are you doing today?
It sounds like your cluster startup delay could be due to a few common issues. First, double-check your AWS VPC and security group settings to ensure they allow the necessary connections. Also, make sure your account isn’t hitting any EC2 instance quotas, and verify that your IAM roles have the correct permissions. Sometimes, new AWS accounts can have configuration hiccups, so if the problem persists, it might be worth reaching out to Databricks support for a deeper dive. Hope this helps!
Regards,
Brahma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2024 01:11 PM
Hey Brahma,
Thanks for the hints. I actually tried a lot of thinks back and forth and the only thing that finally worked was to create a new workspace. Since this was a new account, that was easy. I suppose something would have gone wrong with the configuration of the resources on AWS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2024 03:02 PM
Hi Suela,
Thanks for your update.
Regards,
Brahma

