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

# Connect to Hivenet Object Storage

> Configure the Hivenet endpoint, signing region, access keys, and required path-style addressing.

Use these settings when connecting an S3-compatible client to Hivenet Object Storage.

## Required settings

| Setting | Value |
| - | - |
| Endpoint URL | `https://eu.s3.hivenet.com` |
| Signing region | `Europe` |
| Addressing style | Path style, explicitly enabled |
| Authentication | AWS Signature Version 4 with your Hivenet access key ID and secret access key |
| Console region label | **EU** |

The signing region is case-sensitive. Use `Europe`, even though the console displays **EU**. Do not substitute an AWS region name.

Use your credential pair from **Object Storage > My keys**. An AWS account is not required to use the AWS CLI or AWS SDKs with the Hivenet endpoint.

## Endpoint changes and regions

The EU endpoint is now `https://eu.s3.hivenet.com`. The previous endpoint, `https://eu.s3.public.hivenet.com`, is deprecated. Update the endpoint in existing client profiles and application configurations, and check that the expected buckets are listed before writing data.

The console and the examples in these guides use EU storage. US access through SDKs and the CLI is planned for release 1.39, using `https://us.s3.hivenet.com` and signing region `NorthAmerica`. Do not treat that planned rollout as confirmation that US access is available to your organization.

The regional clusters have separate bucket and object listings. Credentials can be used across the clusters when access is available, but selecting another endpoint does not move or replicate data.

## Path-style addressing

Hivenet uses one endpoint for the region. The bucket name goes in the URL path:

```text theme={null}
https://eu.s3.hivenet.com/BUCKET_NAME/OBJECT_KEY
```

For example, the object `reports/report.csv` in `my-app-bucket` has this path:

```text theme={null}
https://eu.s3.hivenet.com/my-app-bucket/reports/report.csv
```

This illustrates the address format; it is not an unauthenticated download link.

Set the endpoint to the base URL only. Pass the bucket and object key separately through your client's request parameters.

| Client | Required path-style setting |
| - | - |
| AWS CLI | `s3.addressing_style = path` in the selected profile |
| boto3 | `Config(s3={"addressing_style": "path"})` |
| AWS SDK for JavaScript v3 | `forcePathStyle: true` |
| rclone | `force_path_style = true` |

> [!WARNING]
>
> Hivenet does not provide per-bucket subdomains. Do not rely on your client's automatic or virtual-host addressing default.

## Credentials and request signing

An S3-compatible client uses the secret access key to sign requests. It sends the access key ID as part of the signed authentication information.

You do not send an Object Storage key as a bearer token. The identity and administration APIs used by the console have a separate authentication model and are not the customer S3 endpoint.

Keep credential pairs out of source code. Use protected client profiles, environment variables, or your application's secrets manager.

## Choose a client guide

* [AWS CLI](https://docs.hivenet.com/documentation/object-storage/aws-cli.md): configure a profile and transfer files.
* [Python and JavaScript SDKs](https://docs.hivenet.com/documentation/object-storage/sdks.md): make requests from an application.
* [rclone](https://docs.hivenet.com/documentation/object-storage/rclone.md): copy directories and download buckets or prefixes.

All examples use the same Hivenet endpoint and signing region.

## Use AWS request documentation

The [Amazon S3 API reference](https://docs.aws.amazon.com/AmazonS3/latest/API/API_Operations_Amazon_Simple_Storage_Service.html) describes request and response formats.

Use it for operations listed in [Hivenet S3 compatibility](https://docs.hivenet.com/documentation/object-storage/s3-compatibility.md), with the Hivenet settings above. AWS documentation alone does not establish that a feature, header, or optional behavior is available on Hivenet.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.