dbt Cloud IP ranges

Official dbt Cloud ranges from the vendor's publication, split by purpose: all. The ranges below render live from the signed slash0 feed.

purpose	direction	IPv4	IPv6
`dbt-cloud/all`	ingress	·	·

dbt-cloud/all

Direction: ingress. Ranges dbt Cloud connects from (webhook delivery); use them in security group ingress rules on your receiving endpoints.

loading ranges from the feed…

Terraform

data "ipranges_ingress" "dbt_cloud_all" {
  service = "dbt-cloud"
  purpose = "all"
}

resource "aws_security_group_rule" "dbt_cloud_all" {
  type              = "ingress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_ingress.dbt_cloud_all.ipv4_cidrs
  security_group_id = aws_security_group.app.id
}

keep rules current automatically

Terraform data sources refresh only when you run an apply. The hosted tier publishes the same data via AWS managed prefix lists (slash0.dbt-cloud.all.v4 and so on), shared into your account via AWS RAM: rules reference one pl-… id and update within a minute of a vendor change, with removals held through a 72 hour grace window. Request early access or read how it works.

provenance

Ranges come from dbt Cloud's official publication: https://docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses. Fetched sources:

https://docs.getdbt.com/docs/cloud/about-cloud/access-regions-ip-addresses

Every publish is signed (ECDSA P-256 over the feed index, each service document hash-chained to it) and every range change is recorded in the changelog. Verification steps: security. Provider setup: quickstart.