Hey @pk35 , I did some digging and here is what I found. However, before we get to recovery, the most important step is pinning down exactly what got cancelled, because there are three possibilities and they have very different outcomes.

1. You cancelled the whole Databricks plan (account console, Settings, Manage your plan, Cancel plan). Per the AWS docs this one is permanent. You cannot reactivate a cancelled plan, access to workspaces, notebooks, and data goes away, and any Customer Content in workspaces tied to the subscription is deleted within 30 days of cancellation. Your post is about two weeks old, so if this is your case, that 30-day clock is already partway through and time matters.

2. You deleted just the workspace (plan still active). There is no public self-service restore flow for a deleted workspace on AWS. Any recovery is a support matter and is not guaranteed.

3. You cancelled a Databricks subscription inside AWS Marketplace. This is the hopeful one. The AWS docs are explicit that you cannot cancel your Databricks plan through AWS Marketplace, and cancelling there only removes the Marketplace account as a payment method. If that is what happened, your plan and workspace may still be intact and you may just need to re-add a payment method.

Now the good news on your data. Because your storage is in your own S3 bucket under Unity Catalog, the underlying data is very likely still there. On AWS, when a workspace is deleted the default workspace catalog is retained, and its managed tables and volumes stay registered in the Unity Catalog metastore (the metastore lives at the account level, not inside the workspace). So your continued S3 and Unity Catalog access is a good sign that the data files survived, even if the workspace itself did not.

The harder part is notebooks and jobs. Those live in the Databricks control plane, not in your S3 bucket, so keeping S3 access does not bring them back on its own.

Here is what I would do next:

1. Confirm which of the three scenarios above applies. That decides everything else.
2. Open a Databricks Support case at https://help.databricks.com rather than email alone, ideally as the account admin or owner. If you do email, the correct address is help@databricks.com. Your note shows help@databrics.com, which is missing the k, so it may not have reached anyone. Cases created by email from a non-authorized contact can also get bounced.
3. Give support the specifics up front: account ID, workspace ID and URL, AWS region, approximate cancellation or deletion time, and whether this was a plan cancellation, a workspace deletion, or an AWS Marketplace change.
4. Move quickly. Restore is best-effort with no SLA, and if this was a plan cancellation the 30-day content-deletion window is already running.

One more thing that helps regardless of outcome. If any of your notebooks were Git-linked or deployed with Databricks Asset Bundles or Terraform, you can redeploy them into a fresh workspace without needing the old one restored. Paired with your intact S3 and Unity Catalog data, that gets you most of the way back.

Closing takeaway: figure out what was actually cancelled first, get a properly scoped support case in front of Databricks quickly, and take some comfort that your Unity Catalog data in S3 is the piece most likely to have survived.

References:

• Manage subscription and billing (plan cancellation is permanent, the 30-day content deletion, and the AWS Marketplace payment-method detail): https://docs.databricks.com/aws/en/admin/account-settings/account
• Delete a workspace on AWS (no self-service restore, plus the Unity Catalog catalog retention behavior): https://docs.databricks.com/aws/en/admin/workspace/delete-workspace
• Support and case filing (including the help@databricks.com authorized-contact caveat): https://docs.databricks.com/aws/en/resources/support
• Manage workspace objects (restoring from Trash, which is a different thing from recovering a deleted workspace): https://docs.databricks.com/aws/en/workspace/workspace-objects

Hope this helps, Louis