Skip to content

Commit 7d70c9c

Browse files
Adjust content from production to branch folder structure
1 parent b876db5 commit 7d70c9c

File tree

2 files changed

+10
-46
lines changed

2 files changed

+10
-46
lines changed

src/content/docs/byoip/service-bindings.mdx

Lines changed: 0 additions & 33 deletions
This file was deleted.

src/content/docs/byoip/service-bindings/index.mdx

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -3,34 +3,31 @@ title: IP address service bindings
33
pcx_content_type: concept
44
sidebar:
55
order: 6
6-
label: About
7-
group:
8-
label: Service bindings
9-
6+
label: Service bindings
7+
description: In IP address management, service binding refers to the association of IPs to specific Cloudflare services. Review the available options and the API endpoints to set up service bindings.
108
---
119

1210
Within IP address management, service binding refers to the association of an IP (or a range of IPs) to specific Cloudflare services.
1311

12+
:::note
13+
Service binding operations are currently only available via API. You can find all endpoints and their specifications in the [Cloudflare API documentation](/api/operations/ip-address-management-service-bindings-list-service-bindings).
14+
:::
15+
1416
## Scope
1517

16-
Currently, if you have BYOIP configured with [Magic Transit](/magic-transit/), you can use the [service binding](/api/operations/ip-address-management-service-bindings-list-service-bindings) endpoints to add CDN or Spectrum capabilities on top of Magic Transit.
18+
Currently, if you have BYOIP configured with [Magic Transit](/magic-transit/), you can use the [service binding API](/api/operations/ip-address-management-service-bindings-list-service-bindings) endpoints to add CDN or Spectrum capabilities on top of Magic Transit.
1719

18-
### CDN (Cache)
20+
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.
1921

20-
When you add the CDN service binding, any HTTP requests received via designated IPs are directed into the CDN pipeline (for [Layer 7 processing](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy)) as they land on the Cloudflare network.
22+
### CDN (Cache)
2123

22-
Refer to [Use BYOIP with Magic Transit and CDN](/byoip/service-bindings/magic-transit-with-cdn/) to learn how to set this up.
24+
When you add the CDN service binding, any HTTP requests received via designated IPs are directed into the CDN pipeline (for [Layer 7 processing](/fundamentals/concepts/how-cloudflare-works/#how-cloudflare-works-as-a-reverse-proxy)) as they reach the Cloudflare network.
2325

2426
### Spectrum
2527

2628
Adding [Spectrum](/spectrum/) allows you to benefit from Cloudflare security and performance for Layer 4 traffic.
2729

28-
## API
29-
30-
Service binding operations are currently only available via API. You can find all endpoints and their specifications in the [Cloudflare API documentation](/api/operations/ip-address-management-service-bindings-list-service-bindings).
31-
3230
## Limitations
3331

34-
- It is currently not possible to use both Spectrum and CDN together with the Magic Transit service. You must choose one or the other when upgrading your IPs.
3532
- You must keep Magic Transit as a common base service, spanning all addresses in your prefix.
3633
- Once a service binding is created, its propagation across the Cloudflare network will take four to six hours to complete.

0 commit comments

Comments
 (0)