Overview

Object Storage

Our S3-compatible Object Storage provides you with storage capacity for saving data in "Buckets". Any data you save in your Bucket is saved in a Ceph cluster. If you set the visibility of your Bucket to public, everyone can access the Bucket to view or download files via a URL that follows this format:

https://<bucket-name>.<location>.your-objectstorage.com/<file-name>

Object Storage is mainly used to store and share data as it is not possible to edit any data that you uploaded to a Bucket (objects are immutable). So the main purpose of Object Storage is "WORM", which is short for, "Write once, read many [times]". Here are some example use cases:

• Save (automatic) backups
• Share data via a public URL

Buckets are a stand-alone product that you can use independently of any other cloud resources. Via Cloud Console, you can complete basic tasks such as creating a Bucket or generating credentials. For all other features and functionalities, you need to use our S3-compatible API. Here's how you can use our API:

• Amazon S3 compatible tools ^recommended
• Amazon S3 API with the Hetzner S3 endpoint

In the article "List of supported actions", you can check which S3 features our Object Storage currently supports.

Available endpoints

Pricing

Object Storage has a base price, that is billed per hour with a monthly price cap, regardless of how many Buckets you have.

The base price includes a quota of storage and traffic that accumulates with each hour of Object Storage usage. At the end of the month, the quota you have accumulated during the month is deducted from your total usage across all Buckets.

Storage and traffic in excess of the quota included in the base price are billed separately on a pay-as-you-go basis based on your total account usage.

Unused included quota expires at the end of each month and cannot be carried over to the next month.

For more information about the prices, see hetzner.com/storage/object-storage.

The following is free of charge:

• Ingress traffic
• Internal traffic within the network zone eu-central
• S3 API calls such as PUT, GET, or DELETE

Base price

You are charged for every hour you have at least one active Bucket, even if it's empty. At the end of the month, the storage and traffic consumption of all Buckets across all projects are combined and billed as one.

In the following example, Object Storage is used during the hours of 3 p.m., 4 p.m., 5 p.m., 6 p.m., and 7 p.m., meaning there was at least one Bucket active during each of these hours. Therefore, you will be charged for a total of five full hours.

Included Quota

Months vary in the number of days and therefore the number of hours. Therefore, the maximum quota included in the base price depends on the month.

Seasonal time changes are not taken into account

In the example below, three Buckets (blue, pink, green) were used. These are the only Buckets that were created during the entire month. At the end of the month, the usage is charged like this:

• In total, Object Storage was used for three hours. This accumulates to a total included quota of 3 TB-hours of storage and 0.0045 TB of traffic.
• Within those three hours, the entire 0.0045 TB of traffic and only 2.3 TB-hours of storage were used. This means that 0.7 TB-hours of the included storage quota were not used. Those are now expired.
• Since the usage was within the included quota, no additional costs are charged.

Prices for usage in excess of the included quota

We will bill you for the excess storage and traffic in increments of 100 MB ( = 0.0001 TB). If you don't use the full 1TB, you will be charged less.

The price for additional storage is calculated like this:

(net price * TB-hours) + VAT

Minimum billable object size

Minimum:

• 64 kB

The minimum billable object size is the size that you will be charged for, even if the data actually stored is smaller.

Objects that are smaller than this minimum size are charged as if they had this size.

Resources and Attributes

The following resources and attributes are associated with this feature:

• Name
• Visibility (private public)
• Access key
• Secret key

Note: By default, each key pair is automatically valid for every Bucket within the same project. To increase security, check out the FAQ entry "How do I restrict access per key?".

Limits

• Up to 8 kB of metadata per object
• Up to 5 GB per object in a single PUT operation
• Up to 5 GB per object part in a multi-part upload
• Up to 10,000 parts in a multi-part upload
• Up to 5 TB per object
• Up to 256 active parallel (TCP) sessions per source IP
• Up to 750 requests/s per source IP
• Up to 750 requests/s per Bucket
• Up to 10 Gbit/s per Bucket (read or write)
• Up to 100 TB per Bucket
• Up to 50,000,000 objects per Bucket
• Up to 200 S3 credentials across all projects
• Up to 100 Buckets across all projects