Skip to content
Merged
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: "Dedicated Egress IP for Logpush"
description: "Set up dedicated egress IPs for Logpush using Aegis IPs"
date: "2025-08-22"
---

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.
Copy link
Contributor

@patriciasantaana patriciasantaana Aug 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps this sounds better? Feel free to fix if the logic isn't captured accurately.

Suggested change
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.
Cloudflare Logpush can now deliver logs from using fixed, dedicated egress IPs. Routing Logpush traffic through a Cloudflare zone with Aegis IP improves security and allows your log destination to accept traffic exclusively from trusted Aegis IP addresses.


Highlights:

- Fixed egress IPs ensure your destination only accepts traffic from known addresses.
- Works with any supported Logpush destination.
- Recommended to use a dedicated zone as a proxy for easier management.

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/).