Elastic Cloud IP ranges

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

purpose	direction	IPv4	IPv6
`elastic-cloud/api`	egress	·	·
`elastic-cloud/outbound`	ingress	·	·

elastic-cloud/api

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

loading ranges from the feed…

Terraform

data "ipranges_egress" "elastic_cloud_api" {
  service = "elastic-cloud"
  purpose = "api"
}

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

elastic-cloud/outbound

Direction: ingress. Ranges Elastic 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" "elastic_cloud_outbound" {
  service = "elastic-cloud"
  purpose = "outbound"
}

resource "aws_security_group_rule" "elastic_cloud_outbound" {
  type              = "ingress"
  from_port         = 443
  to_port           = 443
  protocol          = "tcp"
  cidr_blocks       = data.ipranges_ingress.elastic_cloud_outbound.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.elastic-cloud.api.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 Elastic Cloud's official publication: https://www.elastic.co/docs/deploy-manage/security/elastic-cloud-static-ips. Fetched sources:

https://ips.cld.elstc.co/

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.