| purpose | direction | IPv4 | IPv6 |
|---|---|---|---|
braze/connected-content | ingress | · | · |
braze/connected-content
Direction: ingress. Ranges Braze connects from (webhook delivery); use them in security group ingress rules on your receiving endpoints.
loading ranges from the feed…
This purpose currently publishes more IPv4 ranges than the default rules-per-SG quota (60). Each CIDR consumes one rule; the hosted prefix list spends quota once per list instead. Details in the FAQ.
Terraform
data "ipranges_ingress" "braze_connected_content" {
service = "braze"
purpose = "connected-content"
}
resource "aws_security_group_rule" "braze_connected_content" {
type = "ingress"
from_port = 443
to_port = 443
protocol = "tcp"
cidr_blocks = data.ipranges_ingress.braze_connected_content.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.braze.connected-content.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 Braze's official publication: https://www.braze.com/docs/user_guide/messaging/design_and_edit/personalize/connected_content/making_an_api_call. Fetched sources:
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.