Skip to main content
Hivenet Object Storage implements a subset of Amazon S3 operations. This page lists the operations covered by these guides. Use the AWS S3 API reference for request and response formats. Configure the Hivenet endpoint and path-style addressing before using AWS examples.

​
Connection requirements

  • Endpoint: https://eu.s3.hivenet.com.
  • Signing region: Europe.
  • Authentication: AWS Signature Version 4 with a Hivenet access key ID and secret.
  • Addressing: path style, explicitly enabled.
These settings target EU storage. See Connection settings for client-specific options, the deprecated endpoint, and the planned US rollout.

​
Organization access modes

Operation support does not override an organization’s access mode. When a self-service organization’s shared credit balance reaches zero or becomes negative, storage changes to Read only or Disabled, depending on the organization’s configured access mode. Changing modes does not itself delete objects or keys. Stored data continues to accrue charges while access is restricted. Existing presigned share links remain valid until expiry regardless of mode, provided the object still exists. See Usage and billing for restoring access and deletion eligibility after seven days without funds.

​
Documented operations

Presigned URLs are signed requests, not separate S3 operation names. Support for an operation does not establish support for every optional header, feature, or client workflow built around it. An operation absent from this table is not a documented compatibility guarantee.

​
Listing and pagination

Use ListObjectsV2 for new integrations. Follow continuation tokens or use your SDK’s paginator to retrieve more than one response. For clients using V1, use its marker-based pagination. The two pagination formats are different.

​
Upload limits

  • A single PutObject request supports objects up to 5 GB.
  • Use multipart uploads for larger objects, up to Hivenet’s 5 TB per-object limit.
These are API limits. The console handles multipart uploads automatically for larger files. See File size and large transfers for console guidance. Use a managed transfer function when you want the client to handle multipart uploads. A raw PutObject call does not automatically split a file. If you manage multipart uploads directly, complete successful uploads and abort abandoned ones.

​
Deletion behavior

A bucket must be empty before DeleteBucket succeeds. Otherwise, the service returns BucketNotEmpty. The console performs the emptying steps for you. API clients need to list objects, delete them, and then delete the empty bucket. For portable client code, send no more than 1,000 keys per DeleteObjects request, as described by the AWS request specification. Check per-object results and refresh the object list after partial failures or interrupted requests. Do not assume an HTTP success alone means every requested object was deleted.

​
Client guides

Use these guides to configure clients for the documented operations: Client defaults can differ. Keep Hivenet’s endpoint, signing region, and path-style setting explicit, and use Troubleshooting if a request fails.