Skip to content

[Aegis] Separate sections for fetch and connect in workers.mdx #24121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 14, 2025
Merged

[Aegis] Separate sections for fetch and connect in workers.mdx #24121

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bc0c1f8
Create separate sections for fetch and connect
RebeccaTamachiro Aug 1, 2025
d57f246
Disambiguate whenever and use Aegis IPs throughout
RebeccaTamachiro Aug 6, 2025
94483b1
Apply suggestions from code review
RebeccaTamachiro Aug 14, 2025
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
14 changes: 10 additions & 4 deletions src/content/docs/aegis/configuration-options/workers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,14 @@ head:

[Workers](/workers/) provides a serverless execution environment for you to create applications leveraging Cloudflare's global network.

When paired with Aegis, whenever Cloudflare's developer platform needs to access services on your origin, it will use the dedicated IP addresses.
Refer to the sections below for information on how Aegis pair up with Workers.

:::note
For Workers subrequests — meaning requests from one Worker to another — it is expected that different IPs are used. However, requests to external origins made by a Worker invoked via a subrequest will use the dedicated IP addresses.
:::
## `fetch`

[`fetch()` requests](/workers/runtime-apis/fetch/) to access services on your origin will use Aegis IP addresses.

For Workers subrequests — meaning requests from one Worker to another — it is expected that different IPs are used. However, [`fetch()` requests](/workers/runtime-apis/fetch/) to external origins made by a Worker invoked via a subrequest will use Aegis IP addresses.

## `connect`

For [`connect()` requests](/workers/runtime-apis/tcp-sockets/) - which create outbound TCP connections from Workers - Aegis IPs are **not** used.