Connected infrastructure
Your providers remain your providers.
Keep your provider accounts, storage and billing. Rhea Data coordinates supported work across your connections, under the authority you define.
Connector capabilities
Compare connection capabilities.
Start with the environment you use. Then choose the supported operation and credential mode, and validate the path your organization needs.
- 01Configure the connection
Your provider account and credential mode.
- 02Prepare a signed request
The implemented path for that storage family.
- 03Validate the operation
The actual upload, download or movement you need.
A signing path identifies how a request is prepared. It does not establish that a particular transfer has passed validation in your environment.
Amazon S3SigV4 · connection details
Connection and request path
S3-compatible request signing.
Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD.
A bucket, region and credentials permitted for the required object operations.
Upload and download
Validate the selected credential mode, object size and operation in your environment.
Movement between connections
Validate both source and destination, including permissions and the applicable transfer path.
Microsoft Azure Blob StorageService SAS · connection details
Connection and request path
Shared-path PUT adds x-ms-blob-type: BlockBlob.
Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD.
The S3-style multipart helper does not support this provider. Other provider-specific paths need separate validation.
A storage account, container and permission to issue service SAS tokens.
Upload and download
Validate the selected credential mode, object size and operation in your environment.
Movement between connections
Validate both source and destination, including permissions and the applicable transfer path.
Google Cloud StorageGOOG4-RSA-SHA256 · connection details
Connection and request path
RSA-signed storage requests.
Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD.
The S3-style multipart helper does not support this provider. Other provider-specific paths need separate validation.
A bucket and a service account able to sign V4 requests.
Upload and download
Validate the selected credential mode, object size and operation in your environment.
Movement between connections
Validate both source and destination, including permissions and the applicable transfer path.
Oracle Object StorageSigV4 · connection details
Connection and request path
Uses the S3-compatible access path.
Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD.
A bucket with S3-compatible access keys and the regional compatibility endpoint.
Upload and download
Validate the selected credential mode, object size and operation in your environment.
Movement between connections
Validate both source and destination, including permissions and the applicable transfer path.
MinIO / S3-compatibleSigV4 · connection details
Connection and request path
Uses S3-compatible request signing.
Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD.
A reachable S3-compatible endpoint, bucket and access keys.
Upload and download
Validate the selected credential mode, object size and operation in your environment.
Movement between connections
Validate both source and destination, including permissions and the applicable transfer path.
Cloudflare R2SigV4 · connection details
Connection and request path
Shared path uses the account endpoint, path-style addressing and region auto.
Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD.
An R2 bucket, account endpoint and R2 access keys.
Upload and download
Validate the selected credential mode, object size and operation in your environment.
Movement between connections
Validate both source and destination, including permissions and the applicable transfer path.
Compare all six families below. If the table is wider than your screen, scroll within the comparison to see every column.
| Storage family | Connection and request path | Upload and download | Movement between connections |
|---|---|---|---|
| Amazon S3 | SigV4 S3-compatible request signing. Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD. A bucket, region and credentials permitted for the required object operations. | Requires environment validation for the selected credential mode, object size and operation. Signing alone is not a transfer test. | Requires validation on both source and destination, including permissions and the applicable transfer path. |
| Microsoft Azure Blob Storage | Service SAS Shared-path PUT adds x-ms-blob-type: BlockBlob. Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD. The S3-style multipart helper does not support this provider. Other provider-specific paths need separate validation. A storage account, container and permission to issue service SAS tokens. | Requires environment validation for the selected credential mode, object size and operation. Signing alone is not a transfer test. | Requires validation on both source and destination, including permissions and the applicable transfer path. |
| Google Cloud Storage | GOOG4-RSA-SHA256 RSA-signed storage requests. Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD. The S3-style multipart helper does not support this provider. Other provider-specific paths need separate validation. A bucket and a service account able to sign V4 requests. | Requires environment validation for the selected credential mode, object size and operation. Signing alone is not a transfer test. | Requires validation on both source and destination, including permissions and the applicable transfer path. |
| Oracle Object Storage | SigV4 Uses the S3-compatible access path. Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD. A bucket with S3-compatible access keys and the regional compatibility endpoint. | Requires environment validation for the selected credential mode, object size and operation. Signing alone is not a transfer test. | Requires validation on both source and destination, including permissions and the applicable transfer path. |
| MinIO / S3-compatible | SigV4 Uses S3-compatible request signing. Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD. A reachable S3-compatible endpoint, bucket and access keys. | Requires environment validation for the selected credential mode, object size and operation. Signing alone is not a transfer test. | Requires validation on both source and destination, including permissions and the applicable transfer path. |
| Cloudflare R2 | SigV4 Shared path uses the account endpoint, path-style addressing and region auto. Customer-held signing: GET, PUT, HEAD, DELETE. Shared signing: GET, PUT, HEAD. An R2 bucket, account endpoint and R2 access keys. | Requires environment validation for the selected credential mode, object size and operation. Signing alone is not a transfer test. | Requires validation on both source and destination, including permissions and the applicable transfer path. |
Choose the interface for your work.
- People in the workspace
Open permitted files and manage supported file work.
Operations depend on connection permissions and product mode. Sensitive work can require explicit approval.
- Applications through the REST API
Use documented, enabled endpoints with application identity and scopes.
The public REST upload endpoint is disabled (410). Customer-authorized workspace uploads use a separate product pipeline.
- Assistants inside Data
List documents, folders and versions; review document metadata from chat.
The documented assistant interface is read-only metadata, scoped to the permitted organization and read grant. File contents and arbitrary provider mutations are not included.
- Provider request signing
Prepare authorized requests for the six storage families below.
Signing and a connection check do not establish upload/download or movement acceptance in your environment.
- Database connection settings
Configure PostgreSQL, MySQL and Microsoft SQL Server connection types.
Direct SQL query execution is disabled. Configuration is not live query access.
Database configuration is a separate scope.
Connection types: PostgreSQL, MySQL, Microsoft SQL Server. Direct SQL query execution is disabled. A configured connection is not a running database query.