For the complete documentation index, see llms.txt. This page is also available as Markdown.

Cloudflare R2

Connections

Create a new connection and choose Cloudflare as its type.

Provide a Connection Label so you can identify the connection in a list. This is especially important if you need more than one connection of the same type.

Bucket Details

Enter the Cloudflare R2 bucket name shown under R2 > Overview in the Cloudflare dashboard.

For Cloudflare Endpoint, enter the URL listed as S3 API in the Cloudflare dashboard. Do not append the bucket name.

Credentials

Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3.

Cloudflare Access Key - The Cloudflare R2 Access Key ID, as shown in your Cloudflare web portal > My Profile > API Tokens page, or in your Cloudflare web portal > R2 > Overview > Manage R2 API Tokens page.

Cloudflare Secret Key - The Secret Access Key that corresponds to the above Access Key ID, as shown in your Cloudflare web portal > My Profile > API Tokens page, or in your Cloudflare web portal > R2 > Overview > Manage R2 API Tokens page.

Cloudflare is Case Sensitive

Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, MyFile.txt and myfile.txt can be two different files. A case-insensitive system treats those names as the same file.

Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.

Last updated