Databricks IP Ranges – AWS, Azure, GCP

🕐 Last updated: 2026-05-18 04:06:59 UTC

Source JSON Files

Revision / schema version: 1.0

Live: ip-ranges.json — machine-readable IP ranges (AWS, Azure, GCP). Docs: AWS · Azure · GCP

Latest snapshot on this site: ip-ranges-20260518-0406.json

Previous JSON versions: View JSON History

Inbound vs outbound IPs

Inbound — CP IPs that receive your traffic when you call Databricks. Allowlist as destination for your outbound calls to the CP.

Outbound — CP egress IPs (source when the CP initiates traffic to you or the internet). Allowlist as source so traffic from the CP is allowed.

Inbound
Your network → Inbound IPs → Databricks CP
Allowlist as destination

Outbound
Databricks CP → Outbound IPs → Your env / internet
Allowlist as source (egress)

Palo Alto Networks Ready Files

Formatted TXT files for Palo Alto Networks firewalls are available on this page: output/

Files are organized by:

Cloud + type — aws.txt, aws-inbound.txt, aws-outbound.txt, azure.txt, gcp.txt
Cloud + region — aws-us-east-1.txt, azure-eastus.txt, gcp-us-central1.txt (emitted only when the region has ≥1 CIDR)

Use the per-region files in production to scope firewall rules to your actual workspace regions instead of allowlisting the entire cloud. Download the file you need and import it into your PA firewall configuration, EDL, AWS Managed Prefix List, Azure IP Group, or GCP Firewall Policy.

Automation-Friendly Design

This page was created to simplify the integration of Databricks IP ranges into firewalls. The project provides a static link to the latest JSON and per-cloud TXT files so you can automate allowlisting without parsing the official API response each time.

Databricks IP Ranges Script

This page is automatically generated using a Python script available at GitHub Repository, and updated regularly through GitHub Actions.

We recommend forking this script if you plan to automate your infrastructure with it. Forking ensures you maintain control of updates, can customize it for your environment, and enhance security by avoiding dependencies on this repository.

Features

Fetches the latest Databricks IP ranges JSON (AWS, Azure, GCP)
Processes and organizes IP ranges by cloud and type (inbound/outbound)
Generates individual TXT files per cloud/type compatible with PA firewalls (one CIDR per line)
Generates per-region TXT files (<cloud>-<region>.txt) so consumers can scope firewall rules to actual workspace regions
Provides a static JSON link and optional history of JSON snapshots
Maintains a history of JSON files for reference

Note: Databricks may update IP ranges periodically. Always verify the ranges against your requirements before implementation. Availability may vary by cloud and region.

Contact

Connect on LinkedIn · Reach on GitHub

Generated on 2026-05-18 04:06:59 UTC by GitHub Automation

This page, its contents, and the associated repository are provided "AS IS" without warranty of any kind. Please refer to the README in the repository for the full disclaimer.