> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataraven.io/llms.txt
> Use this file to discover all available pages before exploring further.

# S3 Compatible

> Connect any S3-compatible provider not covered by a first-class integration.

The catch-all type for any S3-compatible provider without a first-class integration — MinIO,
Storj, IDrive e2, Ceph, and anything else that speaks the S3 API.

<Tip>
  If your provider has its own page in this section, prefer that type over S3 Compatible — it
  gets provider-specific endpoint handling, validation, and task defaults.
</Tip>

## At a Glance

|                   |                                                   |
| ----------------- | ------------------------------------------------- |
| **Region**        | Depends on provider                               |
| **Endpoint URL**  | Required                                          |
| **Credentials**   | Access key — `access_key_id`, `secret_access_key` |
| **Task defaults** | `s3_no_check_bucket: true`                        |

## Credentials

Create a [secret](/secrets) with the **S3 Compatible** provider type. The auth method is
`s3_compatible_access_key`, which requires:

| Field               | Description                  |
| ------------------- | ---------------------------- |
| `access_key_id`     | Provider's access key ID     |
| `secret_access_key` | Provider's secret access key |

The key needs permission to **list, read, write, and delete** objects in the bucket — the same
operations [connection verification](/connecting-storage#connection-verification) tests.

## Location Setup

| Field             | Value                                              |
| ----------------- | -------------------------------------------------- |
| **region**        | Depends on provider — set it if yours requires one |
| **endpoint\_url** | Always required                                    |

Example:

| Field          | Example value               |
| -------------- | --------------------------- |
| name           | `MinIO On-Prem`             |
| location\_type | S3 Compatible               |
| bucket\_name   | `acme-minio`                |
| endpoint\_url  | `https://minio.example.com` |

## Provider Quirks

Many managed S3 providers don't expose `CreateBucket` permission, which surfaces as
`403 Access Denied` during transfers. S3 Compatible locations default to
`s3_no_check_bucket: true` to bypass that check.

## Importing from rclone.conf

A `type = s3` remote whose `provider =` value isn't recognized — including `provider = Other` —
imports as S3 Compatible, with its endpoint and credentials carried over. The exception:
`provider = Other` remotes whose endpoint hostname identifies
[Fil One](/providers/fil-one), [Filebase](/providers/filebase), [Tigris](/providers/tigris), or
[MEGA S4](/providers/mega-s4) are upgraded to those first-class types instead. See the
[rclone import guide](/guides/import-rclone-config).