- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-23-2024 08:54 PM
In azure databricks, it is able to access azure resources and databricks apis using unified MS Entra Id tokens, Similary how can i able to access aws resources and databricks apis (workspace created in cloudformation) using unified access tokens. Here i use sts to access aws resources currently.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-24-2024 04:04 AM
By setting up the IAM role and instance profile, and configuring your Databricks clusters to use the instance profile, you can achieve unified access to AWS resources. For Databricks API access, using OAuth tokens or Databricks PAT tokens ensures secure and managed authentication.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-24-2024 04:20 AM
I will try to validate on why this is the case, but I have confirmed that indeed for API calls in AWS the token needs to be Databricks generated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-24-2024 04:04 AM
By setting up the IAM role and instance profile, and configuring your Databricks clusters to use the instance profile, you can achieve unified access to AWS resources. For Databricks API access, using OAuth tokens or Databricks PAT tokens ensures secure and managed authentication.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-24-2024 04:14 AM
But there is an option to access APIs using MS Entra ID service principal authentication in Azure and Google Cloud Platform Credential Authentication in GCP,
Why cloud provider-based token management is not available in AWS ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-24-2024 04:20 AM
I will try to validate on why this is the case, but I have confirmed that indeed for API calls in AWS the token needs to be Databricks generated.

