Skip to content
Merged
Show file tree
Hide file tree
Changes from all 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
18 changes: 15 additions & 3 deletions src/content/docs/aegis/setup.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ sidebar:
hideIndex: true
---

import { APIRequest } from "~/components";
import { APIRequest, Render } from "~/components";

You can control Aegis enablement on your zones [via API](/api/resources/zones/subresources/settings/methods/edit/). If you are not familiar with how Cloudflare API works, refer to [Fundamentals](/fundamentals/api/).

Expand All @@ -20,7 +20,7 @@ Cloudflare Aegis is available in early access to Enterprise customers. Contact y
- The Aegis zone setting endpoint is only available within Cloudflare accounts that own leased IPs, or accounts to which a [BYOIP prefix](/byoip/) has been delegated. If you wish to use Aegis for zones that do not meet this criteria, contact your account team.
- Each Aegis pool can consist of either IPs from a BYOIP prefix or Cloudflare-leased IPs. A single dedicated egress pool cannot contain both BYOIPs and leased IPs.

## Steps
## Turn on Aegis for a zone

1. Contact your account team to get the ID for your dedicated egress pool.
2. Make a `PATCH` request to the [Edit Zone Setting](/api/resources/zones/subresources/settings/methods/edit/) endpoint:
Expand All @@ -40,4 +40,16 @@ Cloudflare Aegis is available in early access to Enterprise customers. Contact y
parameters={{
setting_id: "aegis",
}}
/>
/>

## Check your Aegis IPs

<Render
file="check-leased-ips"
product="byoip"
params={{
product: "Aegis IPs (dedicated IPs for CDN egress)"
}}
/>

If you are using BYOIP, refer to [**IP addresses** > **BYOIP prefixes**](https://dash.cloudflare.com/?to=/:account/ip-addresses/ip-prefixes) instead.
14 changes: 13 additions & 1 deletion src/content/docs/byoip/concepts/static-ips.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ sidebar:

---

import { Render } from "~/components";

Lease static IPs so that you can use a set of specifically assigned Cloudflare IPs. If you need to allowlist your IPs or to communicate your IPs to third parties, allocating static IPs to your account allows you to know them ahead of time.

Cloudflare will not change static IP addresses without notifying you, and will typically only do so at your request.
Expand All @@ -18,4 +20,14 @@ Static IPs are allocated to the account, but can be assigned to a single zone. T

## Availability

Static IPs are available as an add-on purchase for Enterprise plans.
Static IPs are available as an add-on purchase for Enterprise plans.

## Check Static IPs

<Render
file="check-leased-ips"
product="byoip"
params={{
product: "Static IPs for CDN Ingress"
}}
/>
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar:
order: 1
---

import { Details } from "~/components";
import { Details, Render } from "~/components";

:::note
Only available as an add-on to Zero Trust Enterprise plans.
Expand Down Expand Up @@ -38,14 +38,28 @@ To check if your device is using the correct dedicated egress IP:

When testing against another origin, you may see either an IPv4 or IPv6 address. Gateway has no control over whether connections are made over IPv4 or IPv6. Some origins are only available over IPv4, while others are only available over IPv6. When both protocols are supported, the decision is made by the operating system and browser on the client device. For example, Windows will by default [favor IPv6](https://learn.microsoft.com/troubleshoot/windows-server/networking/configure-ipv6-in-windows) over IPv4.

## Bring your own IP address (BYOIP)
## IPs

### Bring your own IP address (BYOIP)

Enterprise users can use their own authority-provided IPv4 and IPv6 addresses as dedicated egress IPs. Gateway supports bringing your own IPv4 and IPv6 addresses. To obtain an IPv6 range, refer to [American Registry for Internet Numbers (ARIN)](https://www.arin.net/resources/guide/ipv6/first_request/) or [Regional Internet Registry for Europe, Middle East and Central Asia (RIPE NCC)](https://www.ripe.net/manage-ips-and-asns/ipv6/request-ipv6/).

After you onboard your IP addresses, the IP addresses will appear when you create a [egress policy](/cloudflare-one/policies/gateway/egress-policies/) and choose **Use dedicated egress IPs (Cloudflare or BYOIP)** as the [egress method](/cloudflare-one/policies/gateway/egress-policies/#egress-methods). BYOIP dedicated egress IPs do not support [IP geolocation](#ip-geolocation).

For more information, refer to [Cloudflare BYOIP](/byoip/) or contact your account team.

### Cloudflare IPs

If you do not have your own authority-provided IPv4 and IPv6 addresses, you can use dedicated egress IPs with a Cloudflare IP address.

<Render
file="check-leased-ips"
product="byoip"
params={{
product: "Gateway dedicated egress IPs"
}}
/>

## Limitations

### Concurrent connections
Expand Down
10 changes: 10 additions & 0 deletions src/content/docs/magic-transit/cloudflare-ips.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,13 @@ import { Render } from "~/components"
mtLpStaticRoute: "/magic-transit/how-to/configure-routes/#configure-static-routes",
mtLpBgpPeering: "/magic-transit/how-to/configure-routes/#configure-bgp-routes"
}} />

## Check your Cloudflare IPs

<Render
file="check-leased-ips"
product="byoip"
params={{
product: "Anycast IPs for Magic Transit"
}}
/>
14 changes: 12 additions & 2 deletions src/content/docs/spectrum/about/static-ip.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,9 @@ weight: 0

---

import { APIRequest } from "~/components"
import { APIRequest, Render } from "~/components"

When you create a Spectrum application, you are assigned an IP. These IPs are normally dynamic, meaning that they will change over time. But, for instance, if you want to set up WAF custom rules for specific IPs, you may want to use static IPs.
When you create a Spectrum application, you are assigned an IP. These IPs are normally dynamic, meaning that they will change over time. But, for instance, if you want to set up WAF custom rules for specific IPs, you may want to use static IPs.

A static IP, like a physical street address can tell other computers or servers on the Internet where a specific computer is located or connected. This makes the device easier to find on the network, since the IP will not change.

Expand Down Expand Up @@ -48,3 +48,13 @@ When creating a Spectrum application through the API, specify the static IPs tha
}
}}
/>

## Check your static IPs

<Render
file="check-leased-ips"
product="byoip"
params={{
product: "static IPs for Spectrum"
}}
/>
6 changes: 6 additions & 0 deletions src/content/partials/byoip/check-leased-ips.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
---
params:
- product
---

A list of your leased {props.product} is available on the dashboard under [**IP addresses** > **Leased IPs**](https://dash.cloudflare.com/?to=/:account/ip-addresses/leased-ips).