Retool IP ranges

Official Retool ranges from the vendor's publication, split by purpose: default-region. The ranges below render live from the signed slash0 feed.

purpose	direction	IPv4	IPv6
`retool/default-region`	ingress	·	·

retool/default-region

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

loading ranges from the feed…

Terraform

data "ipranges_ingress" "retool_default_region" {
  service = "retool"
  purpose = "default-region"
}

resource "aws_security_group_rule" "retool_default_region" {
  type              = "ingress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_ingress.retool_default_region.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.retool.default-region.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 Retool's official publication: https://docs.retool.com/data-sources/reference/ip-allowlist-cloud-orgs. Fetched sources:

https://docs.retool.com/data-sources/reference/ip-allowlist-cloud-orgs

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.