[Rules] Add R2 to Cloud Connector (#18451)

* Add R2 provider
* Add changelog entry

Author: pedrosousa

src/content/changelogs/rules.yaml

@@ -5,12 +5,15 @@ productLink: "/rules/"
 productArea: Application performance
 productAreaLink: /fundamentals/reference/changelog/performance/
 entries:
+  - publish_date: "2024-11-22"
+    title: Support for Cloudflare R2 object storage in Cloud Connector
+    description: |-
+      You can now connect to R2 buckets in [Cloud Connector](/rules/cloud-connector/).
   - publish_date: "2024-10-23"
     title: Simplified user interface for URL Rewrites with wildcard support
     description: |-
       The new simplified user interface for [URL Rewrites](/rules/transform/url-rewrite/) is now live, making it easier for users to configure URL rewrites with wildcard support. This update streamlines the process by eliminating the need for complex functions in rule creation.
       The updated user interface is available at **Rules** > **Transform Rules** > **Rewrite URL**. For more information, refer to the [wildcard support documentation](/rules/transform/url-rewrite/reference/parameters/#wildcard-matching-and-replacement).
-
   - publish_date: "2024-09-20"
     title: Automatic DNS Validation for Cloudflare Rules
     description: |-

src/content/docs/rules/cloud-connector/create-api.mdx

@@ -34,7 +34,7 @@ The following table summarizes the available operations.
 
 | Operation                                  | Verb + Endpoint                              |
 | ------------------------------------------ | -------------------------------------------- |
-| List Cloud Connector rules                 | `GET /zones/{zone_id}/cloud_connector/rules`  |
+| List Cloud Connector rules                 | `GET /zones/{zone_id}/cloud_connector/rules` |
 | Create/update/delete Cloud Connector rules | `PUT /zones/{zone_id}/cloud_connector/rules` |
 
 ## Example API calls
@@ -84,15 +84,15 @@ curl --request PUT \
 --data '[
   {
     "expression": "http.request.uri.path wildcard \"/images/*\"",
-    "provider": "aws_s3",
-    "description": "Connect to S3 bucket containing images",
+    "provider": "cloudflare_r2",
+    "description": "Connect to R2 bucket containing images",
     "parameters": {
-      "host": "examplebucketwithimages.s3.north-eu.amazonaws.com"
+      "host": "mybucketcustomdomain.example.com"
     }
   }
 ]'
 ```
 
 The required body parameters for each rule are: `expression`, `provider`, and `parameters.host`.
 
-The `provider` value must be one of the following: `aws_s3`, `azure_storage`, and `gcp_storage`.
+The `provider` value must be one of the following: `cloudflare_r2`, `aws_s3`, `azure_storage`, and `gcp_storage`.

src/content/docs/rules/cloud-connector/create-dashboard.mdx

@@ -14,9 +14,10 @@ To configure a Cloud Connector rule in the dashboard:
 
 2. Go to **Rules** > **Cloud Connector**.
 
-3. Select your [cloud provider](/rules/cloud-connector/providers/).
+3. Select your [cloud provider](/rules/cloud-connector/providers/) (Cloudflare R2 or an external provider).
 
-4. Enter the bucket URL and select **Next**.
+4. If you selected Cloudflare R2 in the previous step, select your bucket and your custom domain, and select **Next**.<br/>
+   If you selected a different storage provider, enter the bucket URL and select **Next**.
 
    :::caution
    The bucket URL must follow a [specific format](/rules/cloud-connector/providers/) according to your provider.

src/content/docs/rules/cloud-connector/index.mdx

@@ -13,11 +13,7 @@ head:
 
 import { FeatureTable } from "~/components";
 
-Cloud Connector (beta) allows you to route matching incoming traffic from your website to a public cloud provider that you define such as AWS, Google Cloud, and Azure. With Cloud Connector you can make Cloudflare the control center for your web traffic, including traffic served from public cloud providers, without having to configure additional rules.
-
-:::note
-Support for Cloudflare R2 will be added soon.
-:::
+Cloud Connector (beta) allows you to route matching incoming traffic from your website to a public cloud provider that you define: [Cloudflare R2](/r2/) object storage or an external provider such as AWS, Google Cloud, and Azure. With Cloud Connector you can make Cloudflare the control center for your web traffic, including traffic served from public cloud providers, without having to configure additional rules.
 
 ## How it works
 

src/content/docs/rules/cloud-connector/providers.mdx

@@ -9,13 +9,16 @@ import { Render } from "~/components";
 
 Cloud Connector currently supports the following cloud providers and services:
 
+- Cloudflare R2
 - Amazon Web Services - S3
 - Google Cloud Platform - Cloud Storage
 - Microsoft Azure - Blob Storage
 
-:::note
-Support for Cloudflare R2 will be added soon.
-:::
+## Cloudflare R2
+
+The Cloudflare R2 bucket must be public and [exposed using a custom domain](/r2/buckets/public-buckets/). Buckets exposed using an `r2.dev` subdomain are not supported.
+
+Additionally, the custom domain must be defined in the same zone where you are configuring the Cloud Connector rule.
 
 ## Amazon Web Services - S3