Highlighting the capabilities of the Databricks platform, this repo contains ready-to-use code samples, how-to guides, and deployment architectures to help you learn and operate the Databricks Lakehouse on Azure, AWS, and GCP.
- Azure: adb4u — Azure Databricks security & deployment guides
- AWS: awsdb4u — AWS Databricks deployment & best practices
- GCP: gcpdb4u — GCP Databricks best practices and architecture
- REST API: databricks-rest-api-collection — Postman collections for Databricks REST APIs
- Jump Start: databricks-jump-start — Curated code samples and tutorials
- Focus: Security, governance, and production-ready deployment patterns for Azure Databricks.
- Topics: ADLS Gen2 integration, AAD authentication for REST APIs, platform tokens and secrets management, IP access policies, BYOK (customer-managed keys), ARM templates, and Secure Deployments.
- Folder:
adb4u— see the folder for example templates, notebooks, and step-by-step guides.
- Focus: Deploying and operating Databricks on AWS with best practices for networking, identity, and storage.
- Topics: VPC design, S3 data access patterns, IAM roles and policies, cross-account setups, and automation templates.
- Folder:
awsdb4u— repository of AWS-specific deployment references and example configurations.
- Focus: GCP-specific guidance for Databricks, with emphasis on data plane security and Google Cloud integrations.
- Topics: VPC and subnet design, GCS connectors, IAM & service accounts, KMS integration, and data exfiltration prevention patterns.
- Folder:
gcpdb4u— explore guides and architecture notes for GCP deployments.
- Pick the cloud folder that matches your target environment:
adb4u,awsdb4u, orgcpdb4u. - Follow the README in that folder for deployment steps, architecture diagrams, and sample templates.
- Use the
databricks-rest-api-collectionanddatabricks-jump-startfor API tooling and hands-on examples.
Contributions are welcome. Please open issues or pull requests for documentation improvements, additional cloud scenarios, or new templates.
This repository follows the licensing described in the project; please see the LICENSE file (if present) or reach out for clarification.