Sahidya/dedicated-egress-ip-logoush (#24639)

* sahidya/ibm_cloud_logs

* Delete 2025-08-06-IBM-cloud-logs-integration.mdx

* dedicated-egress-ip-logpush

* Update src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx

Co-authored-by: Patricia Santa Ana <[email protected]>

---------

Co-authored-by: Patricia Santa Ana <[email protected]>

Author: 2 people

src/content/changelog/logs/2025-08-22-dedicated-egress-ip-logpush.mdx

@@ -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.
+
+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, refer to the [Logpush documentation](/logs/logpush/logpush-job/enable-destinations/egress-ip/).