From d928f9e70ce2c66e2fcc2a1839617d68be0d7ae7 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 9 Jan 2025 10:54:43 +0000 Subject: [PATCH 1/5] Style guide adjustments and consistently use 2nd person --- .../cloudflare-for-saas/saas-customers/how-it-works.mdx | 8 ++++---- .../cloudflare-for-saas/saas-customers/index.mdx | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx index e34743457c76901..d8669f603378b1d 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx @@ -9,9 +9,9 @@ head: --- -Orange-to-Orange (O2O) is a specific traffic routing configuration where traffic routes through two Cloudflare zones: the first Cloudflare zone is owned by customer 1 and the second Cloudflare zone is owned by customer 2, who is considered a SaaS Provider. +Orange-to-Orange (O2O) is a specific traffic routing configuration where traffic routes through two Cloudflare zones: the first Cloudflare zone is owned by customer 1 and the second Cloudflare zone is owned by customer 2, who is considered a SaaS provider. -If one or more hostnames are onboarded to a SaaS Provider that uses Cloudflare products as part of their platform, specifically the [Cloudflare for SaaS product](/cloudflare-for-platforms/cloudflare-for-saas/), those hostnames will be created as Custom Hostnames in the SaaS Provider's zone. The Custom Hostnames must be activated to give the SaaS Provider permission to route traffic for the hostname through their zone. +If one or more hostnames are onboarded to a SaaS Provider that uses Cloudflare products as part of their platform, specifically the [Cloudflare for SaaS product](/cloudflare-for-platforms/cloudflare-for-saas/), those hostnames will be created as [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) in the SaaS Provider's zone. The custom hostnames must be activated by the SaaS customer to give the SaaS provider permission to route traffic for the hostname through their zone. ## Without O2O @@ -37,9 +37,9 @@ B --> C ## With O2O -If you have your own Cloudflare zone and your zone contains a **Proxied** DNS record matching the Custom Hostname with a **CNAME** target provided by the SaaS Provider, then O2O will be enabled. +If you have your own Cloudflare zone and your zone contains a **proxied** DNS record matching the custom hostname with a **CNAME** target provided by the SaaS Provider, then O2O will be enabled. -With O2O enabled, the settings configured in your Cloudflare zone will be applied to the traffic first, and then the settings configured in the SaaS Provider's zone will be applied to the traffic second. +With O2O enabled, the settings configured in your Cloudflare zone will be applied to the traffic first, and then the settings configured in the SaaS provider's zone will be applied to the traffic second. ```mermaid flowchart TD diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx index 82f1a27096f46a8..a8fc8e00798d5c4 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/index.mdx @@ -13,7 +13,7 @@ import { DirectoryListing } from "~/components" Cloudflare partners with many [SaaS providers](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/) to extend our performance and security benefits to your website. -Cloudflare customers can take this process a step further by managing their own zone on Cloudflare. This setup - known as **Orange-to-Orange (O2O)** - allows them to benefit from their provider's setup but still customize how Cloudflare treats incoming traffic to their zone. +If you are a SaaS customer, you can take this process a step further by managing your own zone on Cloudflare. This setup - known as **Orange-to-Orange (O2O)** - allows you to benefit from your provider's setup but still customize how Cloudflare treats incoming traffic to your zone. ## Related resources From 062c5f7e121d0479c49925fa5021aa527938d366 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 9 Jan 2025 11:14:12 +0000 Subject: [PATCH 2/5] Fix example breaking mermaid diagram in getting-started --- .../cloudflare-for-saas/start/getting-started.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx index 321e0ab208c377d..f651ca8d3c52443 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx @@ -53,7 +53,7 @@ To finish the custom hostname setup, your customer needs to set up a `CNAME` rec Your customer's `CNAME` record might look like the following: ```txt -www.mystore.com CNAME customers.saasprovider.com +mystore.example.com CNAME customers.saasprovider.com ``` This record would route traffic in the following way: @@ -61,13 +61,13 @@ This record would route traffic in the following way: ```mermaid flowchart TD accTitle: How traffic routing works with a CNAME target -A[Request to www.mystore.com] --> B[customers.saasprovider.com] +A[Request to mystore.example.com] --> B[customers.saasprovider.com] B --> C[proxy-fallback.saasprovider.com] ```
-Requests to `www.mystore.com` would go to your `CNAME` target (`customers.saasprovider.com`), which would then route to your fallback origin (`proxy-fallback.saasprovider.com`). +Requests to `mystore.example.com` would go to your `CNAME` target (`customers.saasprovider.com`), which would then route to your fallback origin (`proxy-fallback.saasprovider.com`). [^1]: From ed01300dcc6d27a846daec4c8d1337322ec5d7eb Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 9 Jan 2025 11:28:23 +0000 Subject: [PATCH 3/5] Bring 'With O2O' higher and provide intro to the CNAME record --- .../saas-customers/how-it-works.mdx | 34 ++++++++++--------- 1 file changed, 18 insertions(+), 16 deletions(-) diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx index d8669f603378b1d..75937fa4a70cc74 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx @@ -11,50 +11,52 @@ head: Orange-to-Orange (O2O) is a specific traffic routing configuration where traffic routes through two Cloudflare zones: the first Cloudflare zone is owned by customer 1 and the second Cloudflare zone is owned by customer 2, who is considered a SaaS provider. -If one or more hostnames are onboarded to a SaaS Provider that uses Cloudflare products as part of their platform, specifically the [Cloudflare for SaaS product](/cloudflare-for-platforms/cloudflare-for-saas/), those hostnames will be created as [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) in the SaaS Provider's zone. The custom hostnames must be activated by the SaaS customer to give the SaaS provider permission to route traffic for the hostname through their zone. +If one or more hostnames are onboarded to a SaaS Provider that uses Cloudflare products as part of their platform - specifically the [Cloudflare for SaaS product](/cloudflare-for-platforms/cloudflare-for-saas/) - those hostnames will be created as [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) in the SaaS Provider's zone. -## Without O2O +To give the SaaS provider permission to route traffic through their zone, any custom hostname must be activated by you (the SaaS customer) by placing a [CNAME record](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#3-have-customer-create-cname-record) on your authoritative DNS. If your authoritative DNS is Cloudflare, you have the option to [proxy](/fundamentals/concepts/how-cloudflare-works/#application-services) your CNAME record, achieving an Orange-to-Orange setup. -If you do not have your own Cloudflare zone and have only onboarded one or more of your hostnames to a SaaS Provider, then O2O will not be enabled. -Without O2O enabled, the settings configured in the SaaS Provider's zone will be applied to the traffic. +## With O2O + +If you have your own Cloudflare zone and your zone contains a **proxied** DNS record matching the custom hostname with a **CNAME** target provided by the SaaS Provider, then O2O will be enabled. + +With O2O enabled, the settings configured in your Cloudflare zone will be applied to the traffic first, and then the settings configured in the SaaS provider's zone will be applied to the traffic second. ```mermaid flowchart TD -accTitle: Your zone using a SaaS provider, but without O2O +accTitle: O2O-enabled traffic flow diagram A[Website visitor] subgraph Cloudflare - B[SaaS Provider-owned zone] + B[Customer-owned zone] + C[SaaS Provider-owned zone] end -C[SaaS Provider Origin] +D[SaaS Provider Origin] A --> B B --> C +C --> D ``` +## Without O2O -## With O2O - -If you have your own Cloudflare zone and your zone contains a **proxied** DNS record matching the custom hostname with a **CNAME** target provided by the SaaS Provider, then O2O will be enabled. +If you do not have your own Cloudflare zone and have only onboarded one or more of your hostnames to a SaaS Provider, then O2O will not be enabled. -With O2O enabled, the settings configured in your Cloudflare zone will be applied to the traffic first, and then the settings configured in the SaaS provider's zone will be applied to the traffic second. +Without O2O enabled, the settings configured in the SaaS Provider's zone will be applied to the traffic. ```mermaid flowchart TD -accTitle: O2O-enabled traffic flow diagram +accTitle: Your zone using a SaaS provider, but without O2O A[Website visitor] subgraph Cloudflare - B[Customer-owned zone] - C[SaaS Provider-owned zone] + B[SaaS Provider-owned zone] end -D[SaaS Provider Origin] +C[SaaS Provider Origin] A --> B B --> C -C --> D ``` From 11a27481398f9f25d979ddb3018acfb073efc74c Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 9 Jan 2025 11:36:45 +0000 Subject: [PATCH 4/5] Add CNAME record example to how-it-works --- .../saas-customers/how-it-works.mdx | 14 +++++++++++++- .../cloudflare-for-saas/start/getting-started.mdx | 2 +- 2 files changed, 14 insertions(+), 2 deletions(-) diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx index 75937fa4a70cc74..670e6ee4038864f 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx @@ -9,6 +9,8 @@ head: --- +import { Example } from "~/components"; + Orange-to-Orange (O2O) is a specific traffic routing configuration where traffic routes through two Cloudflare zones: the first Cloudflare zone is owned by customer 1 and the second Cloudflare zone is owned by customer 2, who is considered a SaaS provider. If one or more hostnames are onboarded to a SaaS Provider that uses Cloudflare products as part of their platform - specifically the [Cloudflare for SaaS product](/cloudflare-for-platforms/cloudflare-for-saas/) - those hostnames will be created as [custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) in the SaaS Provider's zone. @@ -18,7 +20,17 @@ To give the SaaS provider permission to route traffic through their zone, any cu ## With O2O -If you have your own Cloudflare zone and your zone contains a **proxied** DNS record matching the custom hostname with a **CNAME** target provided by the SaaS Provider, then O2O will be enabled. +If you have your own Cloudflare zone (`example.com`) and your zone contains a [proxied DNS record](/dns/manage-dns-records/reference/proxied-dns-records/) matching the custom hostname (`mystore.example.com`) with a **CNAME** target defined by the SaaS Provider, then O2O will be enabled. + + + +DNS management for **example.com** + +| **Type** | **Name** | **Target** | **Proxy status** | +| -------- | ------------ | --------------------------------- | ---------------- | +| `CNAME` | `mystore` | `customers.saasprovider.com` | Proxied | + + With O2O enabled, the settings configured in your Cloudflare zone will be applied to the traffic first, and then the settings configured in the SaaS provider's zone will be applied to the traffic second. diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx index f651ca8d3c52443..149e050ea2c3c80 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started.mdx @@ -32,7 +32,7 @@ The `CNAME` target — optional, but highly encouraged — provides a friendly a -| **Type** | **Name** | **IPv4 address** | **Proxy status** | +| **Type** | **Name** | **Target** | **Proxy status** | | -------- | ------------ | --------------------------------- | ---------------- | | `CNAME` | `.customers` | `proxy-fallback.saasprovider.com` | Proxied | From ec29d52173bbe1feefe3a62fc00f9a094db939eb Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 9 Jan 2025 17:36:43 +0000 Subject: [PATCH 5/5] Nit: Remove redundant 'Step' in H3s --- .../cloudflare-for-platforms/get-started-per-hostname.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx index 376261a93283e48..a05b83630a25d97 100644 --- a/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx +++ b/src/content/partials/cloudflare-for-platforms/get-started-per-hostname.mdx @@ -7,7 +7,7 @@ import { Render, TabItem, Tabs } from "~/components" You need to perform the following steps for each custom hostname. -### Step 1 — Plan for validation +### 1. Plan for validation Before you create a hostname, you need to plan for: @@ -24,7 +24,7 @@ Depending on which method you select for each of these options, additional steps ::: -### Step 2 — Create custom hostname +### 2. Create custom hostname After planning for certification and hostname validation, you can create the custom hostname.