🎉 What’s new

As a data engineer or admin, you’ll want this new setup flow for dbt connections because you can now select your preferred cloud storage and authentication method—ensuring a smoother, more secure integration that fits your company’s needs.

This is a major enhancement: now, when you connect dbt Core in Atlan, you can choose between S3, GCS, or ADLS and specify credentials using IAM roles, user keys, or service accounts—right from the config tab. Previously, setting up secure dbt access was one-size-fits-all and required more back-and-forth with support. Now, setup is flexible, transparent, and built for your cloud provider and security requirements.

✨ Let’s dig deeper

• You can choose your storage provider (S3, GCS, or ADLS) and authentication method directly during dbt connector setup
• For S3: enter IAM User credentials (AWS key, secret, region) or IAM Role (Role ARN, region)
• For GCS: enter your project ID and service account JSON (coming soon for all users)
• For ADLS: provide Azure tenant ID, client ID, client secret, storage account, and container names
• Your credential details are never shown in the UI after entry—for security
• When updating existing connections, fields will be empty by default; you’ll need to re-enter credentials for security, but connections will keep running as is until you do

👏 Give it a shot

• Go to your dbt connector’s profile and open the config tab
• Click the new credential tile to select your storage provider and input credentials
• Follow the prompts for your chosen method (S3, GCS, or ADLS)
• You’ll need admin access to update or set up credentials
• For more help, read the full setup guide.

Now you can connect dbt your way—securely, flexibly, and with total control.