Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/content/docs/data-localization/how-to/r2.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,15 +32,15 @@ The following instructions will show you how to set up a Logpush job using an S3

<Details header="Generate a token for a specific bucket (recommended)">

Go to the R2 section of your Cloudflare dashboard and select **Manage R2 API Tokens** to generate a token directly tied to your specific bucket. You can follow the instructions in the [Authentication](/r2/api/s3/tokens/) section.
Go to the R2 section of your Cloudflare dashboard and select **Manage R2 API Tokens** to generate a token directly tied to your specific bucket. You can follow the instructions in the [Authentication](/r2/api/s3/tokens/) section.

</Details>

<Details header="Generate a token for all buckets">

You can generate a API token in **Manage Account** > **Account API Tokens** or you can create a user-specific token:

1. Go to **My Profile** > **API Tokens**
1. Go to **My Profile** > **API Tokens**
2. Select **Create Token** > **Create Custom Token**
3. Choose **Account** > **Workers R2 Storage** > **Edit** to set permissions.
4. To test your token, copy the `curl` command and paste it into a terminal.
Expand Down Expand Up @@ -71,12 +71,12 @@ The result:
```

5. Generate a SHA-256 hash of the token:

```bash
echo -n "<token>" | shasum -a 256
```

This command will output a hash similar to `dxxxx391b`.
This command will output a hash similar to `dxxxx391b`.

</Details>

Expand Down
6 changes: 3 additions & 3 deletions src/content/docs/data-localization/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -44,11 +44,11 @@ Comply with regional restrictions by choosing which subset of data centers decry
## Related products

<RelatedProduct header="SSL/TLS" href="/ssl/" product="ssl">
Cloudflare SSL/TLS encrypts your web traffic to prevent data theft and other tampering.
Cloudflare SSL/TLS encrypts your web traffic to prevent data theft and other tampering.
</RelatedProduct>

<RelatedProduct header="DNS" href="/dns/" product="dns">
Cloudflare's global DNS platform provides speed and resilience. DNS customers also benefit from free DNSSEC, and protection against route leaks and hijacking.
Cloudflare's global DNS platform provides speed and resilience. DNS customers also benefit from free DNSSEC, and protection against route leaks and hijacking.
</RelatedProduct>

***
Expand All @@ -62,7 +62,7 @@ Refer to our latest resources to learn more about privacy.
</LinkTitleCard>

<LinkTitleCard title="Cloudflare blog" href="https://blog.cloudflare.com/tag/data-localization-suite" icon="open-book">
Read articles about the latest updates to the Data Localization Suite.
Read articles about the latest updates to the Data Localization Suite.
</LinkTitleCard>

</CardGrid>
2 changes: 1 addition & 1 deletion src/content/docs/data-localization/limitations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ There are certain limitations and caveats when using Customer Metadata Boundary.

Specifically most of the Zone Analytics & Logs UI Tabs will be showing up as empty, when configuring Customer Metadata Boundary to EU only. It is recommended to use the UI [Security Analytics](/waf/analytics/security-analytics/) instead, or the [HTTP request](/logs/reference/log-fields/zone/http_requests/) logs via [Logpush](/logs/about/).

To configure Customer Metadata Boundary to EU only, you must disable Log Retention for all zones within your account. Log Retention is a legacy feature of [Logpull](/logs/logpull/).
To configure Customer Metadata Boundary to EU only, you must disable Log Retention for all zones within your account. Log Retention is a legacy feature of [Logpull](/logs/logpull/).

For product-specific caveats, refer to [Cloudflare product compatibility](/data-localization/compatibility/) page.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ To configure Customer Metadata Boundary in the dashboard:

## Configure Customer Metadata Boundary via API

You can also configure Customer Metadata Boundary via API.
You can also configure Customer Metadata Boundary via API.

Currently, only SuperAdmins and Admin roles can edit DLS configurations. Use the **Account-level Logs:Read/Write** API permissions for the `/logs/control/cmb` endpoint to read/write Customer Metadata Boundary configurations.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ sequenceDiagram
participant CloudflarePoP as Closest data center
participant EUCoreDC as Core data center in EU
participant CloudflareSuperAdmin as Admin

UserEU->>CloudflarePoP: Connects
Note right of CloudflarePoP: Customer Logs generated <br> (for example, HTTP requests and Firewall events)
CloudflarePoP-->>EUCoreDC: Forwards encrypted Customer Logs
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ Refer to the table below for the complete list of available regions and their de

## Configure Regional Services via API

You can also use Regional Services via API.
You can also use Regional Services via API.

Currently, only SuperAdmins and Admin roles can edit DLS configurations. Use the Zone-level **DNS: Read/Write** API permission for the `/addressing/` endpoint to read or write Regional Services configurations.

Expand Down