Skip to content

[BYOIP] Service bindings to mix CDN with Spectrum #21368

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 2 commits into from
Apr 7, 2025
Merged

[BYOIP] Service bindings to mix CDN with Spectrum #21368

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bc8ad11
Update Tabs component and add missing Overview Description
RebeccaTamachiro Apr 3, 2025
7a45349
Adjust service-bindings/index.mdx with CDN-Spectrum mix
RebeccaTamachiro Apr 3, 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
6 changes: 5 additions & 1 deletion src/content/docs/byoip/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,11 @@ head:
content: Bringing Your Own IPs to Cloudflare
---

import { LinkButton, Plan } from "~/components";
import { LinkButton, Plan, Description } from "~/components";

<Description>
Get Cloudflare's security and performance while using your own IPs.
</Description>

<Plan type="enterprise" />

Expand Down
7 changes: 4 additions & 3 deletions src/content/docs/byoip/service-bindings/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,11 @@ Service binding operations are currently only available via API. You can find al

## Scope

Customers using BYOIP with Magic Transit can leverage the [service binding API endpoints](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/) to selectively route traffic through the CDN [^1] or Spectrum [^2] pipelines on a per-IP address basis.
Customers using BYOIP with Magic Transit, [CDN services](/cache/), or [Spectrum](/spectrum/) can leverage the [service binding API endpoints](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/) to selectively route traffic through the CDN [^1] or Spectrum [^2] pipelines on a per-IP address basis. This means:

You can upgrade individual IPs within a Magic Transit prefix to either a CDN IP or a Spectrum IP. For example, if you have `203.0.113.0/24`, you can upgrade `203.0.113.1` to CDN and `203.0.113.2` to Spectrum.
- You can upgrade individual IPs within a Magic Transit prefix to either a CDN IP or a Spectrum IP. For example, if you have a Magic Transit prefix `203.0.113.0/24`, you can upgrade `203.0.113.1` to CDN and `203.0.113.2` to Spectrum.
- You can upgrade individual IPs within a CDN prefix to a Spectrum IP. For example, if you have a CDN prefix `203.0.113.0/24`, you can upgrade `203.0.113.1` to Spectrum.
- You can upgrade individual IPs within a Spectrum prefix to a CDN IP. For example, if you have a Spectrum prefix `203.0.113.0/24`, you can upgrade `203.0.113.1` to CDN.

:::caution
Magic Transit customers must ensure that their contract includes CDN and/or Spectrum according to their needs.
Expand All @@ -37,7 +39,6 @@ When a service binding of type `Spectrum` is applied, once the change has propag

## Limitations

- You must keep Magic Transit as a common base service, spanning all addresses in your prefix.
- When adding a service binding for a given IP address, it must be either a CDN service binding or a Spectrum service binding. It is not possible (or necessary) to bind both services.
- Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.

Expand Down
13 changes: 6 additions & 7 deletions src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,8 +134,8 @@ You can choose between two different scopes:
If you need to map only specific subdomains (and not all proxied DNS records) to specific IP addresses, you can use a [Subdomain setup](/dns/zone-setups/subdomain-setup/).
:::

<Tabs labels="Dashboard | API">
<TabItem label="dashboard" no-code="true">
<Tabs syncKey="dashPlusAPI">
<TabItem label="Dashboard" no-code="true">

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
2. Go to **IP Addresses** > **Address Maps**.
Expand All @@ -146,7 +146,7 @@ If you need to map only specific subdomains (and not all proxied DNS records) to
7. Review the information and select **Save and Deploy**.

</TabItem>
<TabItem label="api" no-code="true">
<TabItem label="API" no-code="true">

Use the [Create Address Map](/api/resources/addressing/subresources/address_maps/methods/create/) endpoint.

Expand All @@ -157,8 +157,8 @@ Make sure you have the correct Key/Token and permissions.

## 4. Create DNS records

<Tabs labels="Dashboard | API">
<TabItem label="dashboard" no-code="true">
<Tabs syncKey="dashPlusAPI">
<TabItem label="Dashboard" no-code="true">

To create a DNS record in the dashboard:

Expand All @@ -170,8 +170,7 @@ To create a DNS record in the dashboard:
6. Select **Save**.

</TabItem>

<TabItem label="api" no-code="true">
<TabItem label="API" no-code="true">

To create records with the API, use a [POST request](/api/resources/dns/subresources/records/methods/create/). For field definitions, select a record type under the request body specification.

Expand Down