diff --git a/products/byoip/src/content/about/index.md b/products/byoip/src/content/about/index.md deleted file mode 100644 index fd521ee43542a9e..000000000000000 --- a/products/byoip/src/content/about/index.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -title: Getting Started -weight: 1 ---- - -## Bringing Your Own IPs to Cloudflare - -BYOIP is compatible with Magic Transit, Spectrum, and CDN services. - -In order to bring your own IPs (BYOIP) with Cloudflare you’ll need to go through an onboarding process. Work with your account team to understand everything we will need to ensure a smooth transition. - -At a high level in order for a prefix to be onboarded to Cloudflare there will be a service specific configuration required, as well as some requirements that are common to all BYOIP customers, regardless of service type. This documentation will cover the requirements common to all products that are compatible with BYOIP (i.e. Magic Transit, CDN, and Spectrum). - -There are two major prerequisites before Cloudflare can begin the work of onboarding your IP space. - -First, all customers must ensure their [Internet Route Registry (IRR)](/byoip/irr) records are up to date with the correct prefix/ASN information. - -Secondly, Cloudflare must receive a [Letter of Authorization](/byoip/loa) to announce your prefixes, which we will share with our transit partners as evidence we are allowed to announce the route. - -Optionally, if you use the RPKI protocol to sign your routes, Cloudflare can support you there as well. Just let your account team know if you're interested in using RPKI! - -Please see the subsequent sections to learn more. - -Once onboarded, BGP announcements for customer prefixes can be controlled with the [Dynamic Advertisement API](/byoip/api). This API has other useful features and can also be used via the Cloudflare dashboard. diff --git a/products/byoip/src/content/api/index.md b/products/byoip/src/content/api/index.md deleted file mode 100644 index 901fbc289f3a72e..000000000000000 --- a/products/byoip/src/content/api/index.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Dynamic Advertisement -weight: 3 ---- - -Toggling on/off a BGP advertisement by the Cloudflare edge is a simple API call, or UI toggle. You can authorize a call with your email and api key, or create a [service token](https://support.cloudflare.com/hc/en-us/articles/200167836-Managing-API-Tokens-and-Keys) for this purpose. You may also toggle/on advertisement in the UI, but will be asked to confirm the action. - -**You may toggle the advertisement status of a prefix once every 15 minutes, and it may take up to ten minutes for an advertisement/withdrawal to take effect.** - -Additionally, you can add free text descriptions to your prefixes. - - -A successful response from the API means our service registered the request, the actual withdrawal/announcement may take up to ten minutes to take affect. - -Finally, the API/UI support adding 'delegations' to your prefixes. Delegations allow other Cloudflare accounts interact with your prefix. The effect of a 'delegation' is service specific, so please see the ##delegations## section to learn more. - -To toggle advertisement status from the UI simple click into the IP Prefixes product - located on the account home page, and click 'edit' on an invdividual prefix. - - -![Advertisement status ui]( - ../static/prefix_ui.png) - -From the dropdown 'Status' - either select 'Withdrawn' or 'Advertised', then click save. You will be asked to confirm you choice. - -API users can find all the calls documented here: [API docs](https://api.cloudflare.com/#ip-address-management-dynamic-advertisement-properties) along with examples. - diff --git a/products/byoip/src/content/dynamic-advertisement/best-practices.md b/products/byoip/src/content/dynamic-advertisement/best-practices.md new file mode 100644 index 000000000000000..9818fd2300e41b3 --- /dev/null +++ b/products/byoip/src/content/dynamic-advertisement/best-practices.md @@ -0,0 +1,53 @@ +--- +order: 2 +--- + +# Best practices + +-------- + +## Verify User Roles & Obtain Prefix IDs + +To ensure smooth operation in general and simplify the advertisement process during an attack scenario, complete the following tasks: + +* **Assign appropriate user roles.** Ensure that users assigned to manage the status of IP prefix advertisement have the Administrator or Super Administrator role in your Cloudflare account. For instructions, see [_Setting up Multi-user accounts on Cloudflare_](https://support.cloudflare.com/hc/en-us/articles/205065067-Setting-up-Multi-User-accounts-on-Cloudflare#12345682). + +* **Get a list of the Prefix IDs you want to manage.** Maintaining a list of Cloudflare IDs for each prefix simplifies management via the Cloudflare API, since most dynamic advertisement operations require them. + + To obtain Prefix IDs, go your Cloudflare account home page and review [_Get Prefix IDs_](/api/configure-prefixes#get-prefix-ids), or use the [List Prefixes](https://api.cloudflare.com/#ip-address-management-prefixes-list-prefixes) operation in the Cloudflare API. Refer to these Prefix IDs when managing prefix advertisement. + +-------- + +## Enable prefix advertisement + + + +To avoid latency and the possibility of dropped routes, enable prefix advertisement from Cloudflare **before** you withdraw the advertisement from your data center, as outlined in these steps: + +1. To enable prefix advertisement, [use the IP Prefixes page](/api/configure-prefixes#use-the-ip-prefixes-page-to-configure-dynamic-advertisement) in your Cloudflare account home or use the [Update Prefix Dynamic Advertisement Status](https://api.cloudflare.com/#ip-address-management-dynamic-advertisement-get-advertisement-status) operation in the Cloudflare API. This operation requires your Account ID, Prefix IDs, and API key. (For instructions, see [_Get Prefix IDs_](/api/configure-prefixes#get-prefix-ids).) + + Enablement takes 2–7 minutes. + +2. Verify the advertisement using looking glass of your choice—[Hurricane Electric Internet Services](https://lg.he.net/), for example. Use the Cloudflare ASN (13335) to track the advertisement route. + +3. Remove the prefix advertisement that originates from your data center. + +-------- + +## Disable prefix advertisement + +To disable (withdraw) prefix advertisement, reverse the steps you used to enable it: + +1. Add the prefix advertisement to your data center. + +2. [Optional] Verify the advertisement using a looking glass of your choice—[Hurricane Electric Internet Services](https://lg.he.net/), for example. + +3. To disable prefix advertisement at Cloudflare’s edge, see the [IP Prefixes page](/api/configure-prefixes#use-the-ip-prefixes-page-to-configure-dynamic-advertisement) in your Cloudflare account home or use the [Update Prefix Dynamic Advertisement Status](https://api.cloudflare.com/#ip-address-management-dynamic-advertisement-get-advertisement-status) operation in the Cloudflare API. This operation requires your Account ID, Prefix IDs, and API key. (For instructions, see [_Get Prefix IDs_](/api/configure-prefixes#get-prefix-ids) + +Disablement takes approximately 15 minutes. diff --git a/products/byoip/src/content/dynamic-advertisement/configure-dynamic-advertisement.md b/products/byoip/src/content/dynamic-advertisement/configure-dynamic-advertisement.md new file mode 100644 index 000000000000000..2581d0b8764fb2e --- /dev/null +++ b/products/byoip/src/content/dynamic-advertisement/configure-dynamic-advertisement.md @@ -0,0 +1,65 @@ +--- +order: 3 +--- + +# Configure dynamic advertisement + + + +-------- + +## Use the IP Prefixes page to configure dynamic advertisement + +To configure IP prefix assignment from your Cloudflare account home, use the **Status** drop-down list in the **IP Prefixes** dialog, as outlined in these steps: + +1. Log in to your Cloudflare accounts **Home** page and click **IP Prefixes**. + + ![account home](../static/dashboard-home-ip-prefixes.png) + + The **IP Prefixes** page displays. + +2. To edit a prefix, click the **Edit** link associated with the entry. + + ![ip-prefixes-list](../static/ip-prefixes-page.png) + + The **Edit IP Prefixes** dialog displays. + + ![ip prefixes dialog](../static/dashboard-dynamic-advertisement.png) + +1. To configure prefix advertisement, select the _Advertised_ or _Withdrawn_ option from the **Status** drop-down list. + + ![status drop-down list](../static/dynamic-advertisement-status-drop-down.png) + +4. Click **Save** to commit your changes. + +Once you have committed your changes, it takes 2–7 minutes to enable advertisement and approximately 15 minutes to disable (withdraw) advertisement. + +-------- + +## Use the Cloudflare API to configure dynamic advertisement + +To configure prefix advertisement with the Cloudflare API, use the [IP Address Management and Dynamic Advertisement](https://api.cloudflare.com/#ip-address-management-dynamic-advertisement-properties) API. + +Most dynamic advertisement operations require that you supply the Cloudflare ID for any prefix you want to access with the Cloudflare API. The following section outlines how to obtain Prefix IDs. + +-------- + +## Get Prefix IDs + +You can obtain Prefix IDs from the **IP Prefixes** page in your Cloudflare account home or via the [List Prefixes](https://api.cloudflare.com/#ip-address-management-prefixes-list-prefixes) operation in the Cloudflare API. + +To obtain Prefix IDs from the **IP Prefixes** page, follow these steps: + +1. Click the expander widget associated with the entry for which you want to obtain the Prefix ID. + + ![prefix-detail-expander](../static/ip-prefixes-expander.png) + + The prefix details display. + +2. To obtain the Prefix ID, refer to the **API Tag** value. To add the value to your clipboard, click **Copy**. + + ![prefix details view](../static/ip-prefix-details-view.png) diff --git a/products/byoip/src/content/dynamic-advertisement/index.md b/products/byoip/src/content/dynamic-advertisement/index.md new file mode 100644 index 000000000000000..64f9648a413ac4c --- /dev/null +++ b/products/byoip/src/content/dynamic-advertisement/index.md @@ -0,0 +1,19 @@ +--- +order: 2 +--- + +# Dynamic Advertisement + +To configure BGP advertisement at the Cloudflare edge, [use the Cloudflare API](/api/configure-prefixes#use-the-cloudflare-api-to-configure-dynamic-advertisement) or [use the IP Prefixes page](/api/configure-prefixes#use-the-ip-prefixes-page-to-configure-dynamic-advertisement) in your Cloudflare account home. + +When using the API, you can authorize a call with your email and API key, or create a [service token](https://support.cloudflare.com/hc/en-us/articles/200167836-Managing-API-Tokens-and-Keys) for this purpose. + +A successful API response indicates the service registered the request. It typically takes 2–7 minutes to enable advertising and approximately 15 minutes to disable it. + +Both the API and Cloudflare UI support prefix delegations, which allow other Cloudflare accounts to interact with your prefix. The effect of a delegation is service specific. For details, see [Prefix Delegations](/delegations). + + \ No newline at end of file diff --git a/products/byoip/src/content/getting-started/index.md b/products/byoip/src/content/getting-started/index.md new file mode 100644 index 000000000000000..accecfa5c050b80 --- /dev/null +++ b/products/byoip/src/content/getting-started/index.md @@ -0,0 +1,27 @@ +--- +order: 1 +--- + +# Getting Started + +-------- + +## Bringing Your Own IPs to Cloudflare + +BYOIP is compatible with Magic Transit, Spectrum, and CDN services. + +To bring your own IPs (BYOIP) with Cloudflare, you must go through an onboarding process. Work with your account team to understand everything you need to ensure a smooth transition. + +At a high level, Cloudflare requires a service-specific configuration for your prefixes, as well as some requirements that are common to all BYOIP customers, regardless of service type. This documentation covers the requirements common to all products that are compatible with BYOIP (i.e. Magic Transit, CDN, and Spectrum). + +There are two major prerequisites before Cloudflare can begin the work of onboarding your IP space. + +First, all customers must ensure their [Internet Routing Registry (IRR)](/irr) records are up to date with the correct prefix/ASN information. + +Secondly, Cloudflare must receive a [Letter of Authorization](/loa) to announce your prefixes, which we will share with our transit partners as evidence that we are allowed to announce the route. + +Optionally, if you use the RPKI protocol to sign your routes, Cloudflare can support you there as well. Just let your account team know if you’re interested in using RPKI! + +Please see the subsequent sections to learn more. + +Once onboarded, BGP announcements for customer prefixes can be controlled with the [Dynamic Advertisement API](/api). This API has other useful features and can also be used via the Cloudflare dashboard. diff --git a/products/byoip/src/content/index.md b/products/byoip/src/content/index.md index 00d83664d448aca..eed03e5623a0168 100644 --- a/products/byoip/src/content/index.md +++ b/products/byoip/src/content/index.md @@ -1,7 +1,10 @@ --- +title: Welcome order: 0 --- -# Welcome +# Cloudflare BYOIP documentation -TODO... +With BYOIP, Cloudflare announces your IPs in all our locations. Use your IPs with Magic Transit, Spectrum, or CDN services. + +

Get started

\ No newline at end of file diff --git a/products/byoip/src/content/irr-records/best-practices-for-irr-entry-updates.md b/products/byoip/src/content/irr-records/best-practices-for-irr-entry-updates.md new file mode 100644 index 000000000000000..7fdeaba9a94b30d --- /dev/null +++ b/products/byoip/src/content/irr-records/best-practices-for-irr-entry-updates.md @@ -0,0 +1,59 @@ +--- +order: 6 +--- + +# Best practices for IRR entry updates + +To add or update an IRR entry, use one of the routing registries listed in the [Internet Routing Registry](http://www.irr.net/index.html). + +Suggested registries are AFRINIC, APNIC, ARIN, NTT, RADB, and RIPE. + +-------- + +## Best practices + +When updating IRR entries, use these best practices: + +* If you own your own subnet, use the RIPE and APNIC routing registries. These registries allow you to verify subnet ownership. +* If you lease your subnet, follow these guidelines: + * When you do not need ownership verification, use the AFRINIC or NTT routing registry. + * When you submit a route object via email, use the ARIN registry. Note that address blocks owned by others do not appear in the ARIN interface. + +### IRR Entry instructions + +Each routing registry has its own set of IRR entry instructions. This table provides links to those instructions: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Route registryURL
AFRINIChttps://afrinic.net/internet-routing-registry#guide
APNIChttps://www.apnic.net/manage-ip/apnic-services/routing-registry/
ARINhttps://www.arin.net/resources/manage/irr/quickstart/
NTThttps://www.gin.ntt.net/support-center/policies-procedures/routing-registry/
RADBhttps://www.radb.net/faq
RIPEhttps://www.ripe.net/manage-ips-and-asns/db/support/managing-route-objects-in-the-irr
diff --git a/products/byoip/src/content/irr-records/index.md b/products/byoip/src/content/irr-records/index.md new file mode 100644 index 000000000000000..bd5991e4fe1bfa3 --- /dev/null +++ b/products/byoip/src/content/irr-records/index.md @@ -0,0 +1,15 @@ +--- +order: 1 +--- + +# IRR Records + +The [Internet Routing Registry (IRR)](http://www.irr.net/index.html) is a globally distributed database of routing information. The IRR contains announced routes and routing policy in a common format. Network operators use this information to configure their backbone routers. + +The IRR consists of many individual [routing registries](http://www.irr.net/docs/list.html), some managed by regional entities, such as APNIC, ARIN, and RIPE. Each routing registry contains IRR entries that provide information about IP prefixes and the [autonomous systems](https://www.cloudflare.com/learning/network-layer/what-is-an-autonomous-system/) that are authorized to announce them. + +To announce your subnet prefixes, Cloudflare requires accurate IRR entries for your prefixes and autonomous system numbers (ASNs). + +When you configure network infrastructure for services such as [Magic Transit](https://developers.cloudflare.com/magic-transit/about), [verify your IRR entries](/irr/verify-irr-entries). + +When you add missing IRR entries or update inaccurate ones, use these [best practices](/irr/best-practices-for-irr-entry-updates). diff --git a/products/byoip/src/content/irr-records/verify-irr-entries.md b/products/byoip/src/content/irr-records/verify-irr-entries.md new file mode 100644 index 000000000000000..7883a61cc9311d9 --- /dev/null +++ b/products/byoip/src/content/irr-records/verify-irr-entries.md @@ -0,0 +1,96 @@ +--- +order: 4 +--- + +# Verify IRR Entries + +Verify your Internet Routing Registry (IRR) entries to ensure that the IP prefixes Cloudflare advertises for you match the correct autonomous system numbers (ASNs). + +Each IRR entry record must include the following information: + +* **Route:** each IP prefix that Cloudflare advertises for you. +* **Origin AS:** your ASN, or if you do not have your own ASN, the Cloudflare ASN (AS209242). +* **Source:** the name of the routing registry—for example, AFRINIC, APNIC, ARIN, RADB, RIPE, or NTT. + +[Add or update IRR entries](/irr/best-practices-for-irr-entry-updates) when they meet any of these criteria: + +* The entry is missing. +* The entry is incomplete or inaccurate—for example, when the route object does not show the correct origin. +* The entry is complete but requires updating—for example, when they correspond to supernets but need to correspond to subnets used in Magic Transit. + +-------- + +## IRR entry verification methods + +To verify your prefix and ASN route, use the tools and methods outlined in this table: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Data to verifyToolMethodOutput
Subnet prefix IP for the ASNIRR ExplorerSearch for the subnet prefix IP, for example, 162.211.156.0/24.List of ASN numbers, source (route registry), and any associated errors.
ASN for the subnet prefixIRR ExplorerSearch for the ASN, for example AS209242.List of prefixes, source, and any associated errors.
Your origin ASN and routing dataWHOIS lookup +

In a terminal, use this whois command, substituting your network prefix for network-prefix:

+

whois -h rr.ntt.net network-prefix

+

The host rr.ntt.net is the primary server for the Global IP network.

+ 		IRR route, origin, and source information.
+ +### WHOIS output example + +The `` in the WHOIS output shows the correct IRR entry information for the specified network. In this example, the network prefix is 1.1.1.0/24, and the output includes the route, origin ASN, and route registry, which in this example is APNIC: + +```txt +user@xxt32z conduit-qs-config % whois -h rr.ntt.net 1.1.1.0/24 +route: 1.1.1.0/24 + +descr: RPKI ROA for 1.1.1.0/24 +remarks: This route object represents routing data retrieved from the RPKI +remarks: The original data can be found here: https://rpki.gin.ntt.net/r/AS13335/1.1.1.0/24 +remarks: This route object is the result of an automated RPKI-to-IRR conversion process. +remarks: maxLength 24 +origin: AS13335 +mnt-by: MAINT-NTTCOM-RPKI +changed: job@ntt.net 20200913 +source: RPKI # Trust Anchor: apnic + + +route: 1.1.1.0/24 +origin: AS13335 +descr: APNIC Research and Development + 6 Cordelia St +mnt-by: MAINT-AU-APNIC-GM85-AP +last-modified: 2018-03-16T16:58:06Z +source: APNIC +``` + + diff --git a/products/byoip/src/content/irr/index.md b/products/byoip/src/content/irr/index.md deleted file mode 100644 index 5eb23e920f8b8ff..000000000000000 --- a/products/byoip/src/content/irr/index.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: IRR Records -weight: 2 ---- - -The Internet Route Registry (IRR) is a globally distributed database of routing information. The IRR is made up of many individual datasources, some managed by regional entities such as RIPE, APNIC, and ARIN. - -Each datasource contains routing information about particular prefixes and which ASNs are authorized to announce them. All routing information is compiled across these different sources and used to inform backbone router configuration. - -Before Cloudflare will announce your prefixes it is important that the IRR entries for your prefixes reflect the right information (i.e. the prefixes and ASN match what you want Cloudflare to announce). diff --git a/products/byoip/src/content/irr/updating-irr-records.md b/products/byoip/src/content/irr/updating-irr-records.md deleted file mode 100644 index 1db4864e9f28a56..000000000000000 --- a/products/byoip/src/content/irr/updating-irr-records.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Updating IRR Records -weight: 4 ---- -### Where to Update IRR Records - -You may update the IRR record in the regional registry's database that your IPs belong to. - -Please see the below links for the getting started guides from three popular registries. - -[ARIN](https://www.arin.net/resources/manage/irr/quickstart/) - -[RIPE](https://www.ripe.net/manage-ips-and-asns/db/support/managing-route-objects-in-the-irr) - -[APNIC](https://www.apnic.net/about-apnic/whois_search/about/what-is-in-whois/irr/) diff --git a/products/byoip/src/content/loa/index.md b/products/byoip/src/content/loa/index.md index 0d251bdf54bd22f..d2f40a4f594526e 100644 --- a/products/byoip/src/content/loa/index.md +++ b/products/byoip/src/content/loa/index.md @@ -1,7 +1,9 @@ --- -title: "Letter of Authorization (LOA)" -weight: 10 +order: 10 --- + +# Letter of Authorization (LOA) + A letter of authorization (LOA) is a document that authorizes Cloudflare to announce a prefix(es) on behalf of another entity. Some backbone and transit providers require that Cloudflare provide them with an LOA whenever Cloudflare starts to announce a customer prefix. The letter must contain both the prefixes you are authorizing Cloudflare to announce, and which ASN they will be announced under. Cloudflare can announce a prefix under your ASN or you are welcome to use ours. If you want Cloudflare to use our ASN, just let us know and we will provide the AS number to put in the LOA document. diff --git a/products/byoip/src/content/loa/example-template.md b/products/byoip/src/content/loa/loa-template.md similarity index 96% rename from products/byoip/src/content/loa/example-template.md rename to products/byoip/src/content/loa/loa-template.md index 67d0882ed571c15..10e9c931afbf7fa 100644 --- a/products/byoip/src/content/loa/example-template.md +++ b/products/byoip/src/content/loa/loa-template.md @@ -1,8 +1,9 @@ --- -title: 'LOA Template' -weight: 2 +order: 2 --- +# LOA Template + You may use the below template when creating an LOA document. [COMPANY LETTERHEAD] diff --git a/products/byoip/src/content/delegations/index.md b/products/byoip/src/content/prefix-delegations/index.md similarity index 85% rename from products/byoip/src/content/delegations/index.md rename to products/byoip/src/content/prefix-delegations/index.md index bcedba892919091..40b045f237c017a 100644 --- a/products/byoip/src/content/delegations/index.md +++ b/products/byoip/src/content/prefix-delegations/index.md @@ -1,8 +1,9 @@ --- -title: Prefix Delegations -weight: 3 +order: 3 --- +# Prefix Delegations + BYOIP supports prefix delegations. A prefix delegation is when the prefix owner account (Account A), allows use of part or all of the prefix to another account (Account B). The effect of a delegation depends on the service you are using with the prefix. Currently BYOIP + CDN and BYOIP + Spectrum support prefix delegations. See below to learn more about prefix delegations with Spectrum and CDN. @@ -15,7 +16,7 @@ Example: Account A is the primary owner of prefix 1.2.3.4/24. Account A delegate API calls for delegations can be found at [Prefix Delegations](https://api.cloudflare.com/#ip-address-management-prefix-delegation-properties). -In the UI, once you click in to 'Edit' a prefix - you will see the option to create a delegation towards the bottom of the screen. Other accounts your user is a part of will auto-load when you create the delegation. Afterwards just click 'save' and you're all set. +In the UI, once you click in to ‘Edit’ a prefix — you will see the option to create a delegation towards the bottom of the screen. Other accounts your user is a part of will auto-load when you create the delegation. Afterwards just click ‘save’ and you’re all set. ![prefix delegation](../static/prefix_delegations.png) diff --git a/products/byoip/src/content/static/dashboard-dynamic-advertisement.png b/products/byoip/src/content/static/dashboard-dynamic-advertisement.png new file mode 100644 index 000000000000000..9347fe0b3ac60e4 Binary files /dev/null and b/products/byoip/src/content/static/dashboard-dynamic-advertisement.png differ diff --git a/products/byoip/src/content/static/dashboard-home-ip-prefixes.png b/products/byoip/src/content/static/dashboard-home-ip-prefixes.png new file mode 100644 index 000000000000000..06f8eeb1e1a97c6 Binary files /dev/null and b/products/byoip/src/content/static/dashboard-home-ip-prefixes.png differ diff --git a/products/byoip/src/content/static/dynamic-advertisement-status-drop-down.png b/products/byoip/src/content/static/dynamic-advertisement-status-drop-down.png new file mode 100644 index 000000000000000..9e92cbd7311661f Binary files /dev/null and b/products/byoip/src/content/static/dynamic-advertisement-status-drop-down.png differ diff --git a/products/byoip/src/content/static/ip-prefix-details-view.png b/products/byoip/src/content/static/ip-prefix-details-view.png new file mode 100644 index 000000000000000..91753101a91204a Binary files /dev/null and b/products/byoip/src/content/static/ip-prefix-details-view.png differ diff --git a/products/byoip/src/content/static/ip-prefixes-expander.png b/products/byoip/src/content/static/ip-prefixes-expander.png new file mode 100644 index 000000000000000..f15fbee9eccb95c Binary files /dev/null and b/products/byoip/src/content/static/ip-prefixes-expander.png differ diff --git a/products/byoip/src/content/static/ip-prefixes-page.png b/products/byoip/src/content/static/ip-prefixes-page.png new file mode 100644 index 000000000000000..7c7d06a7714ce44 Binary files /dev/null and b/products/byoip/src/content/static/ip-prefixes-page.png differ diff --git a/products/byoip/wrangler.toml b/products/byoip/wrangler.toml index 798495828c5aabf..9c53f2404987cf2 100644 --- a/products/byoip/wrangler.toml +++ b/products/byoip/wrangler.toml @@ -2,12 +2,14 @@ name = "byoip" type = "webpack" account_id = "b54f07a6c269ecca2fa60f1ae4920c99" # cloudflare-docs.workers.dev workers_dev = true +kv_namespaces = [{ binding = "REDIRECTS", id = "b393a548b93e4c36936e9276dedf5f5a", preview_id = "b393a548b93e4c36936e9276dedf5f5a" }] [env.production] workers_dev = false account_id = "b54f07a6c269ecca2fa60f1ae4920c99" zone_id = "351cf9fc660523187714fa772ad5ca49" route = "https://developers.cloudflare.com/byoip*" +kv_namespaces = [{ binding = "REDIRECTS", id = "327898e0657e4e609149720d0353b652", preview_id = "327898e0657e4e609149720d0353b652" }] [site] bucket = ".docs/public/"