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:ย 

Databricks not able to create cluster with Amazon free trial version

SahilRana3097
Visitor

Error : Cannot launch the cluster because the user specified an invalid argument.


Instance ID: failed-2d901c0f-d88d-499a-a

Internal error message: The VM launch request to AWS failed, please check your configuration. [details] InvalidParameterCombination: The specified instance type is not eligible for Free Tier. For a list of Free Tier instance types, run 'describe-instance-types' with the filter 'free-tier-eligible=true'. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 9a0e1bed-c0de-4a15-b06b-3fc44a61b137; Proxy: null)(OnDemand)

What kind of node is compatible with both AWS and Databricks. Is there any was to connect the both
1 ACCEPTED SOLUTION

Accepted Solutions

DivyaandData
Databricks Employee
Databricks Employee

The error is coming from AWS, not Databricks: your AWS account is restricted to Free Tierโ€“eligible instance types, but the node type you picked in Databricks maps to an EC2 instance that is not Free Tierโ€“eligible, so AWS rejects the launch request with InvalidParameterCombination: The specified instance type is not eligible for Free Tier.

1. โ€œCompatibleโ€ nodes between AWS and Databricks

On Databricks on AWS, each node type is just a curated EC2 instance type (driver + workers) that Databricks is allowed to launch in your account (for example, m5.xlarge, m5d.xlarge, r5d.xlarge, m6i.large, etc.).

Databricks only supports specific instance families for nodes (general purpose M, compute-optimized C, memory-optimized R, storage-optimized I/D, GPU G/P, and some fleet types).

AWS Free Tierโ€“eligible instances (like the various `t_micro` types) are not in this supported set, so there is effectively no Databricks node type that is both Free Tierโ€“eligible and supported for clusters.

2. Ways to โ€œconnect bothโ€ / get this working

You canโ€™t attach an existing Free Tier EC2 instance to Databricks; Databricks must create and manage the EC2 nodes itself. The practical options are:

  1. Use a normal (billable) AWS instance family that Databricks supports

    • In the Databricks Compute UI, pick a standard node type such as m5d.xlarge, m6i.large, etc.
       
    • Your AWS account must allow nonโ€“Free Tier instances (no policy blocking them). Youโ€™ll then pay normal EC2 + Databricks DBU costs.
  2. Use Databricks Serverless compute (if available in your region/plan)

    • With Serverless, Databricks manages the underlying instances and you only choose the size / SKU; infra is included in the serverless price, but itโ€™s not Free Tierโ€”youโ€™re still billed through Databricks rather than your EC2 Free Tier.
  3. For learning only: use Databricks Community Edition (separate environment)

    • Community Edition runs on Databricksโ€™ own AWS account with small, managed clusters and does not use your AWS Free Tier at all. Itโ€™s good for demos and notebooks, not for production.

If your goal is โ€œno AWS charges at allโ€ on your own account, then youโ€™ll need to use Community Edition; running a full Databricks workspace on your AWS account inevitably requires paid instance types, not Free Tierโ€“only ones.

View solution in original post

1 REPLY 1

DivyaandData
Databricks Employee
Databricks Employee

The error is coming from AWS, not Databricks: your AWS account is restricted to Free Tierโ€“eligible instance types, but the node type you picked in Databricks maps to an EC2 instance that is not Free Tierโ€“eligible, so AWS rejects the launch request with InvalidParameterCombination: The specified instance type is not eligible for Free Tier.

1. โ€œCompatibleโ€ nodes between AWS and Databricks

On Databricks on AWS, each node type is just a curated EC2 instance type (driver + workers) that Databricks is allowed to launch in your account (for example, m5.xlarge, m5d.xlarge, r5d.xlarge, m6i.large, etc.).

Databricks only supports specific instance families for nodes (general purpose M, compute-optimized C, memory-optimized R, storage-optimized I/D, GPU G/P, and some fleet types).

AWS Free Tierโ€“eligible instances (like the various `t_micro` types) are not in this supported set, so there is effectively no Databricks node type that is both Free Tierโ€“eligible and supported for clusters.

2. Ways to โ€œconnect bothโ€ / get this working

You canโ€™t attach an existing Free Tier EC2 instance to Databricks; Databricks must create and manage the EC2 nodes itself. The practical options are:

  1. Use a normal (billable) AWS instance family that Databricks supports

    • In the Databricks Compute UI, pick a standard node type such as m5d.xlarge, m6i.large, etc.
       
    • Your AWS account must allow nonโ€“Free Tier instances (no policy blocking them). Youโ€™ll then pay normal EC2 + Databricks DBU costs.
  2. Use Databricks Serverless compute (if available in your region/plan)

    • With Serverless, Databricks manages the underlying instances and you only choose the size / SKU; infra is included in the serverless price, but itโ€™s not Free Tierโ€”youโ€™re still billed through Databricks rather than your EC2 Free Tier.
  3. For learning only: use Databricks Community Edition (separate environment)

    • Community Edition runs on Databricksโ€™ own AWS account with small, managed clusters and does not use your AWS Free Tier at all. Itโ€™s good for demos and notebooks, not for production.

If your goal is โ€œno AWS charges at allโ€ on your own account, then youโ€™ll need to use Community Edition; running a full Databricks workspace on your AWS account inevitably requires paid instance types, not Free Tierโ€“only ones.