> For the complete documentation index, see [llms.txt](https://moverdocs.files.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moverdocs.files.com/connections/object-storage/s3-compatible-storage.md).

# S3-Compatible Storage

Mover's S3-compatible connection type lets you connect to private cloud services that speak the S3 protocol, including IBM Cloud, Oracle Cloud, Minio, and DigitalOcean Spaces.

## Connections

Create a new connection and choose <code class="expression">page.vars.VENDOR\_NAME</code> 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 name of the bucket to use for the connection.

Enter the API endpoint for the bucket.

Enter the region where the bucket resides if the provider requires it.

### Credentials

Mover uses an Access Key and Secret Key to authenticate requests, following the protocol established by AWS for S3. Check your storage provider's documentation for how to create the access key and secret key.

## Case Sensitivity

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.

Check the documentation on your storage provider to determine whether you need to account for case sensitivity differences.