How can I resolve a problem between AWS and Databricks platform?

[Algograp_admin]

This is Algograp Co., Ltd., a partner of Databricks.

There was a problem in the process of subscribing to Databricks and linking AWS account.
I had a problem using my existing platform and canceled my subscription. Account activation is not possible during the process of reconnecting and starting the service.

 

In AWS page, we subscribe to Databricks Lakehouse Platform. But, we coudln't connect to admin account for databricks platform.

And when we login to databricks platform, notice that our subscription has been canceled.

I'm trying to link it to a admin account, but I'd appreciate it if you could tell me how to fix it.

Thank you.

[Kaniz_Fatma]

Hi @Algograp_admin, it seems like there are a few potential issues that could be causing the problem with your Databricks subscription and AWS account linkage.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. **Check your AWS account billing information:** Make sure that your AWS account billing information is complete. If it's not, Databricks might be unable to validate your credentials.

2. **Verify your AWS account:** Confirm that there are no issues with your AWS account by verifying that you can launch an EC2 instance.

3. **Check IAM permissions:** It can take a minute or two for IAM to propagate the permissions set on the IAM role or user. If validation fails, retry the configuration in the Databricks account.

4. **Check user registration:** The error message suggests that the user might not be registered in the account console. You can verify if the user is registered using the following command:

bash
curl -n -X GET 'https://accounts.cloud.databricks.com/api/2.0/accounts/<accountID>/scim/v2/Users' | jq '.'

If the user is not registered, you should add them to the account console.

5. **Check your Databricks subscription:** Make sure your Databricks subscription is active and you are using the correct account. If your subscription has been cancelled, you might need to contact Databricks support for further assistance.