services / oracle-cloud

Oracle Cloud Infrastructure IP ranges

Official Oracle Cloud Infrastructure ranges from the vendor's publication, split by purpose: all, object-storage. The ranges below render live from the signed slash0 feed.

purposedirectionIPv4IPv6
oracle-cloud/allegress··
oracle-cloud/object-storageegress··

oracle-cloud/all

Direction: egress. Ranges your workloads connect out to; use them in security group egress rules.

loading ranges from the feed…

Terraform

data "ipranges_egress" "oracle_cloud_all" {
  service = "oracle-cloud"
  purpose = "all"
}

resource "aws_security_group_rule" "oracle_cloud_all" {
  type              = "egress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_egress.oracle_cloud_all.ipv4_cidrs
  security_group_id = aws_security_group.app.id
}

oracle-cloud/object-storage

Direction: egress. Ranges your workloads connect out to; use them in security group egress rules.

loading ranges from the feed…

Terraform

data "ipranges_egress" "oracle_cloud_object_storage" {
  service = "oracle-cloud"
  purpose = "object-storage"
}

resource "aws_security_group_rule" "oracle_cloud_object_storage" {
  type              = "egress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_egress.oracle_cloud_object_storage.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.oracle-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 Oracle Cloud Infrastructure's official publication: https://docs.oracle.com/en-us/iaas/Content/General/Concepts/addressranges.htm. 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.