Skip to content

Commit e441d0d

Browse files
committed
dedicated-egress-ip-logpush
1 parent 083eeea commit e441d0d

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
title: "Dedicated Egress IP for Logpush"
3+
description: "Set up dedicated egress IPs for Logpush using Aegis IPs"
4+
date: "2025-08-22"
5+
---
6+
7+
Cloudflare Logpush can now deliver logs from using fixed, dedicated egress IPs. By routing Logpush traffic through a Cloudflare zone enabled with [Aegis IP](/aegis/), your log destination only needs to allow Aegis IPs making setup more secure.
8+
9+
Highlights:
10+
11+
- Fixed egress IPs ensure your destination only accepts traffic from known addresses.
12+
- Works with any supported Logpush destination.
13+
- Recommended to use a dedicated zone as a proxy for easier management.
14+
15+
To get started, work with your Cloudflare account team to provision Aegis IPs, then configure your Logpush job to deliver logs through the proxy zone. For full setup instructions, see the [documentation](/logs/logpush/logpush-job/enable-destinations/egress-ip/).

0 commit comments

Comments
 (0)