Skip to content

Commit 65d3a86

Browse files
Placeholder page for new get-started and temp hide old one
1 parent f519040 commit 65d3a86

File tree

3 files changed

+39
-2
lines changed

3 files changed

+39
-2
lines changed
Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: Get started
3+
pcx_content_type: get-started
4+
sidebar:
5+
order: 2
6+
---
7+
8+
import { GlossaryTooltip } from "~/components";
9+
10+
Work with your account team to understand everything you need to ensure a smooth transition during the onboarding process.
11+
12+
Cloudflare requires a service-specific configuration for your prefixes, as well as some requirements common to all BYOIP customers regardless of service type.
13+
14+
## Requirements
15+
16+
The following requirements are common to all products compatible with BYOIP.
17+
18+
You must verify that your [Internet Routing Registry (IRR)](/byoip/concepts/irr-entries/) records are up to date and contain:
19+
20+
- `route` or `route6` objects matching the exact prefixes you want to onboard
21+
- `origin` matching the correct ASN you want to onboard
22+
23+
:::caution[RPKI validation]
24+
You are not required to use <GlossaryTooltip term="Resource Public Key Infrastructure (RPKI)">Resource Public Key Infrastructure (RPKI)</GlossaryTooltip>. However, if you do, make sure your <GlossaryTooltip term="Route Origin Authorization (ROA)">ROAs</GlossaryTooltip> are accurate. You can use [Cloudflare's RPKI Portal](https://rpki.cloudflare.com/?view=validator) and a second source such as [Routinator](https://rpki-validator.ripe.net/ui/) to double check your prefixes.
25+
:::
26+
27+
## Process overview
28+
29+
Overall, the steps can be summarized as follows:
30+
31+
1. You revise your IRRs and ROAs (if applicable) to make sure they are correct.
32+
2. You prepare a [letter of agency (LOA)](/byoip/concepts/loa/) containing both the prefixes you are authorizing Cloudflare to announce and which ASN they will be announced under. Cloudflare will present this to our transit partners as evidence that we are allowed to announce the route.
33+
3. After receiving the LOA, Cloudflare validates the [requirements](#requirements).
34+
4. Cloudflare provisions the IPs.
35+
5. Once the IPs are provisioned, you use [service bindings](/byoip/service-bindings/) and [address maps](/byoip/address-maps/) to control how your IPs are used.
36+
6. (Optional) You can use [Prefix delegations](/byoip/concepts/prefix-delegations/) to share all or part of your prefix with another Cloudflare account.
37+
7. Finally, you configure the [Border Gateway Protocol advertisement](/byoip/concepts/dynamic-advertisement/) for your IPs at the Cloudflare network.

src/content/docs/byoip/get-started.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Get started
33
pcx_content_type: get-started
44
sidebar:
55
order: 2
6-
6+
hidden: true
77
---
88

99
import { GlossaryTooltip } from "~/components"

src/content/docs/byoip/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,4 @@ Get Cloudflare's security and performance while using your own IPs.
1818

1919
With **Bringing Your Own IPs** (BYOIP), Cloudflare announces your IPs in all our locations. Use your IPs with [Magic Transit](/magic-transit/), [Spectrum](/spectrum/), [CDN services](/cache/), or [Gateway DNS](/cloudflare-one/policies/gateway/dns-policies/).
2020

21-
Learn how to [get started](/byoip/get-started/).
21+
Learn how to [get started](/byoip/get-started-review/).

0 commit comments

Comments
 (0)