Issue creating a workspace with Databricks Partner Account & AWS Sandbox Environment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago - last edited 2 weeks ago
Subject:
Hello,
My name is Priya, and my organization is a Databricks partner. We've been given access to the Partner Academy, and my company has set up an AWS sandbox environment to support our certification preparation.
I'm currently trying to set up a Databricks workspace using this sandbox environment, integrated with our company’s AWS account. This isn't part of a specific lab or tutorial—I'm simply following the standard process I've used successfully in the past. Typically, I log into my Databricks account, click on “Create Workspace,” and use the Quick Start option, which redirects me to our company’s AWS CloudFormation service to create the stack.
However, I’m encountering an error during the "createWorkspace" step of the AWS CloudFormation stack. I tried creating workspaces in different AWS regions but all face the same issue. Our internal IT support team has said that there are no issues on our AWS side and that I have the necessary permissions. They issue seems to be on the Databricks side, and they’ve advised me to reach out for assistance. I also reached out to the Databricks support team, and they recommended posting here to get help from community engineers.
Some of my colleagues—following the same process—are able to successfully set up their workspaces without any issues. I was able to set it up this way a few months back, and my partner account has not expired yet, but now this approach is not working.
Any guidance or insight into resolving this would be greatly appreciated!
Thank you,
Priya
- Labels:
-
Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Creating a workspace in a different region would not allow the use of the pre-existing UC metastore. Did you try the manual option?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Hi, thanks for the reply. I think for every different region I use, it creates a new metastore, or if a metastore for that region already exists, then it attaches it to the workspace. I did not try the manual option yet, since it is a bit more technically involved as it asks me to create the buckets, policies and roles myself. But I will try that.
Best,
Priya
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago - last edited a week ago
Tried the manual approach, followed all the steps to create bucket, policy, role, credentials etc. But still it fails to create workspace. It doesn't show any logs other than just saying:
"
"
A metastore is attached to it, metastore_aws_us_east_2.
How should I proceed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Does the network configuration created for the new workspace give any additional information about the error? The Databricks account executive assigned to your company and their team may be able to help you further.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
I do not see anything created under network configuration. Private access settings and vpc endpoints both show 403 status when clicking on them, and there is a default policy under network policies. I will reach out to the account executive.

