# S3-Compatible

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.

## Add a <code class="expression">page.vars.VENDOR\_NAME</code> Connection

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

Add the Endpoint for accessing your bucket via API.

Choose the Region where your bucket resides, if required by your provider.

### 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.

## Check For Case Sensitivity

Be aware of case sensitivity differences when copying, moving, or syncing files and folders between connections. Copying items from a system which is not case sensitive to another that is case sensitive could result in 1 item being treated as 2 different ones, such as attempting to overwrite `MyFile.txt` with `myfile.txt` .&#x20;

In the other direction, copying from a case sensitive system to another that is not case sensitive can cause files to be overwritten, and folders to have their contents merged, if their case *insensitive* names are a match.

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://moverdocs.files.com/connections/s3-compatible.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.