Solved: EC2 instances are not stoped after the cluster ter... - Databricks Community - 17109

Register to join the community

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.

I found that Databricks did not stop and delete ec2 instances of clusters. After the cluster terminate , the ec2 instances are still running.

1 ACCEPTED SOLUTION

Accepted Solutions

Please make sure the Databricks IAM role does have all required permission mentioned https://docs.databricks.com/administration-guide/account-api/iam-role.html#0-language-Your%C2%A0VPC,...
Make sure you did not change the EC2 tags especially the reserved ones: ClusterName, RunName (for job clusters), JobId (for job clusters), Creator Name, Vendor ClusterId, Name after the cluster is running.

View solution in original post

1 REPLY 1

Please make sure the Databricks IAM role does have all required permission mentioned https://docs.databricks.com/administration-guide/account-api/iam-role.html#0-language-Your%C2%A0VPC,...
Make sure you did not change the EC2 tags especially the reserved ones: ClusterName, RunName (for job clusters), JobId (for job clusters), Creator Name, Vendor ClusterId, Name after the cluster is running.

never-displayed

You must be signed in to add attachments

never-displayed

Announcements

Announcing Google’s Gemma 3 on Databricks

Share Your Thoughts on Databricks & Select your Swag!

How Data Intelligence is Accelerating IT/OT Convergence

Are you part of a Databricks user group in your city/region?

🚀 INTRODUCING NEW COMBINATIONS! - Monthly Databricks Get Started Days 🚀