cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

DLT error at validation

AlvaroCM
New Contributor III

Hello,

I'm creating a DLT pipeline with Databricks on AWS. After creating an external location for my bucket, I encountered the following error:

DataPlaneException: [DLT ERROR CODE: CLUSTER_LAUNCH_FAILURE.CLIENT_ERROR] Failed to launch pipeline cluster aaaaa-bbbbb-cccc with termination code AWS_AUTHORIZATION_FAILURE and termination type CLIENT_ERROR: Could not launch cluster due to cloud provider authorization failure. databricks_error_message: Failure happened when talking to AWS, AWS API error code: AccessDenied AWS error message: User: arn:a...

This is the full error that the DLT pipeline shows, even in JSON format, so I'm unsure which AWS ARN it's referring to.

Steps to reproduce the error:

  1. I created an External Location.
  2. I attached an empty Notebook script to my Delta Live Tables pipeline (I just want to validate it so far).

When I press "Validate," it throws that error at the "waiting for resources" step in the DLT graph.

My guess is that I'm missing some additional cluster authorization in AWS (IAM) for DLT that I couldn't find in the Databricks documentation.

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions

AlvaroCM
New Contributor III

Hi!

The error was related to the roles and permissions created when the workspace was set up. I reloaded the setup script in a new workspace, and it worked without problems.

Hope it helps anyone in the future.

Thanks!

View solution in original post

2 REPLIES 2

MuthuLakshmi
Databricks Employee
Databricks Employee

@AlvaroCM 
The issue could be because the AWS doesn't have the instance type "waiting for resources" 

Can you use the instance type of the cluster which you were able to create using the clusters UI explicitly over the DLT pipeline as mentioned below.

"node_type_id": "m4.4xlarge",
"driver_node_type_id": "m4.4xlarge"

AlvaroCM
New Contributor III

Hi!

The error was related to the roles and permissions created when the workspace was set up. I reloaded the setup script in a new workspace, and it worked without problems.

Hope it helps anyone in the future.

Thanks!

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now