S3 Compatible: Object Storage adheres to the industry-standard S3 protocol, ensuring seamless integration with S3 Tools and applications designed for S3-compatible platforms. For more information, see S3 API Compatibility.
Data Management: The data storage pool comprising of objects and buckets in a flat data environment is well manageable with the following data management functions:
Replication: Safeguards your data by duplicating it across multiple locations, providing redundancy and ensuring high availability. You can replicate data within user-owned buckets of the same user as well as replication to contract-owned buckets in the eu-central-3 region.
Versioning: Tracks and manages multiple versions of an object, enabling easy rollback of objects and buckets to the previous states and preserving historical versions of objects and buckets.
Lifecycle: Archives or deletes objects based on predefined criteria, optimizing costs and managing data efficiently.
Object Lock: Secures your data by implementing retention policies or legal holds, ensuring that data objects remain immutable for a specified duration or indefinitely. This way, the data meets the Write Once Read Many (WORM) data storage technology and prevents the data from being erased or modified.
Access Management: The following functions allow users to set access permissions to other Object Storage users, defining who can access their objects and buckets.
Access Control List (ACL): A granular permissions for objects and buckets, controlling who can access and modify your data.
Bucket Policy: You can set overarching access policies for a bucket that provides additional security and control over how data is accessed and used.
Logging: Monitors and records access requests to your objects and buckets, providing a clear audit trail and helping identify suspicious activities. This feature is currently not supported for contract-owned buckets.
Cross-Origin Resource Sharing (CORS): Defines rules for client web applications from different domains to access the data resources stored in your buckets.
Public Access: The data in the IONOS Object Storage are well managed by allowing or blocking access permissions to be public access wherever needed with the following functions:
Block Public Access: Ensures data privacy by blocking all public access at the bucket or account level. Currently, this feature is available only via the IONOS Object Storage API.
Static Website Hosting: Using Object Storage, you can host static websites directly, eliminating the need for additional web servers, thus simplifying deployment. You can enable the objects in these buckets with public read access, allowing users to view all the content on these static websites.
Security: Data object protection is achieved through the following:
Encryption in Transit: Secures data as it travels to and from the Object Storage using robust TLS 1.2/1.3 encryption protocol.
Server-Side Encryption: Protects stored data by encrypting it on the server side with IONOS Object Storage managed keys (SSE-S3) and customer-managed keys (SSE-C) using AES256 encryption algorithm. The storage objects are decrypted automatically when downloaded.
Features: IONOS Object Storage secures your data in the storage pool through Versioning, Block Public Access, Object Lock, and Replication features.
Security Certification: The solution adheres to the ISO 27001 certificate based on IT-Grundschutz and complies with the European Union's (EU's) General Data Protection Regulation (GDPR).
Large Data Volume: Data in the Object Storage are stored as objects, which include metadata and a unique identifier, making object retrieval easier for large volumes of unstructured data.
Cost-Effective Billing: A straightforward pay-as-you-go Pricing Model, eliminating upfront costs. You are charged solely based on storage utilization and outbound data transfer per gigabyte. Additionally, we do not impose charges for requests.
Highly Scalable: With Object Storage, you can start with small data storage and expand data storage as your application needs at any time, offering the utmost flexibility with data storage.
Georedundant Hosting: Using Replication, you can replicate objects and buckets in the Object Storage to multiple data centers in different geographical locations, guaranteeing high availability and data durability even during primary site failures or outages. For Replication support based on the bucket types, see Feature Comparison.
Compliance Standards: IONOS Object Storage infrastructure and processes comply with IT-Grundschutz, GDPR, and ISO-27001 standards, offering peak data protection and robust privacy policies.
Write Once Read Many (WORM): The Object Lock on the data stored in the Object Storage is protected and prevents the data from being erased or modified.
Data Protection: With access control lists and Object Lock features, multiple layers of data protection can be enforced on data objects and define permissions for who can access the data in the Object Storage. With advanced data encryption algorithms, secure data storage is achieved.
Lifecycle Management: With Object Storage Lifecycle rules, you can enforce the data deletion process for historical data and save the storage cost.
IONOS Object Storage is a secure, scalable storage solution that offers high data availability and performance. The product adheres to the S3 API standards, enabling the storage of vast amounts of unstructured data and seamless integration into S3-compatible applications and infrastructures.
Unlike traditional hierarchical systems like block storage volumes or disk file systems, Object Storage utilizes a flat structure that is ideal for storing large chunks of unstructured, static data that you want to keep ‘as is’ for later access. Businesses of all sizes can use IONOS Object Storage to store files (objects) for varied Use Cases.
The IONOS Object Storage service is available in the following locations:
| Data Center | Region | Bucket Type |
|---|---|---|
For the list of available points of access, see Endpoints.
In IONOS Object Storage, the data that you want to store in the Object Storage is called Objects. The data types could be archives, backups, log files, documents, images, and media assets. Each object is allocated a unique URL for direct access. Further, you can group these objects within a folder to help organize and manage these objects within a bucket. For more information, see Objects and Folders.
To begin with Object Storage, you need to generate a key, which is a unique identifier that allows you access to buckets and objects. This key is a combination of Access Key and Secret Key, listed in the Key Management section. For more information, see Key Management.
To upload objects into the Object Storage, you need to create containers known as Buckets by choosing the region and a unique bucket name. The objects are stored in these buckets which are accompanied by rich metadata. For more information, see Buckets and Bucket Types.
Based on access permissions, buckets, and objects can be publicly accessible or kept private and shared with only intended users. Use the Access Control List (ACL) or Bucket Policy settings to manage access.
Frankfurt, Germany
de
User-owned buckets
Berlin, Germany
eu-central-2
User-owned buckets
Logroño, Spain
eu-south-2
User-owned buckets
Berlin, Germany
eu-central-3
Contract-owned buckets
IONOS Object Storage provides a range of access options, including DCD, desktop applications, CLI tools, and an option to develop your application using API and SDKs.
In the DCD, go to Menu > Storage > IONOS Object Storage to access IONOS Object Storage via the DCD. Here you can manage buckets, and objects, set access controls, and much more. To set up Object Storage, see Enable Object Storage access.
The Object Storage is fully compatible with S3, using which users can establish seamless integration of Object Storage with existing S3-compatible tools. A few of the popular GUI tools are Postman, Cyberduck, and S3 Browser; and CLI tools are AWS CLI, S3cmd, and rclone. For more information, see S3 Tools.
Being S3 compatible means you can use standard S3 API calls and SDKs with our storage solution. For more information, see IONOS Object Storage API Reference.
The pricing model for IONOS Object Storage is as follows:
1 Gigabyte (GB) is equal to 1024 Megabytes (MB).
Storage space is charged per GB per hour.
Data transfer is charged in GB. Inbound data transfer is free, but it will be counted as outbound data transfer for your Virtual Machine (VM) if you upload data from it. Outbound data transfer can be paid or free, depending on the conditions outlined in Outbound data transfer from IONOS Object Storage.
Using the IONOS Object Storage API is free of charge.
Prices are listed in the respective price lists:
IONOS Ltd. – United Kingdom.
IONOS Inc. – United States and Canada.
All outbound data transfer from IONOS Object Storage is billable as public traffic, except for data transfer to the VMs in the same data center.
The cost per GB for outbound data transfer is contingent upon the cumulative data consumption of the account. A tiered pricing structure is implemented for all outbound traffic, including data transfer from VMs and IONOS Object Storage.
All outbound data transfer from IONOS Object Storage is billed as public traffic. The local and national traffic definitions do not apply. This includes outgoing data transfer to IONOS VMs or dedicated servers regardless of their geographical location.
While inter-bucket data transfer is subject to charges, replication traffic both within the same region and across different regions is cost-free.
The cost per GB for outbound data transfer is contingent upon the cumulative data consumption of the account. A tiered pricing structure is implemented for all outbound traffic, including data transfer from VMs and IONOS Object Storage.
No charges are imposed on inbound data transfer to IONOS Object Storage. It is essential to know that when uploading data to IONOS Object Storage, the same data transfer may be billed as an outbound data transfer for your VM.
While calculating network costs for data transfer from a VM to IONOS Object Storage, the following distinctions are made in the billing based on the traffic type:
| Data Transfer from a VM to IONOS Object Storage | Billing |
|---|---|
Within the confines of the same data center
Local traffic
Located in the same country but at a different data center
National traffic
Located in a data center in a different country
Public traffic
The following are a few limitations to consider while using IONOS Object Storage:
Access keys: A user can have up to five access keys.
Storage size: The minimum storage size available is 1 Byte of data and is extendable to a maximum storage of petabytes.
Bucket naming conventions: Only buckets for static website hosting can use dots (.) in the bucket names. For more information, see bucket Naming conventions.
Bucket count: A user can create up to 1000 contract-owned buckets and 500 user-owned buckets. For more information, see Bucket Types.
Bucket Policy size: The maximum allowed Bucket Policy size for a contract-owned bucket is 1 MiB, and for a user-owned bucket is 20 KiB.
Object size: The maximum allowed object size is 5 TiB.
Object name length: The maximum allowed length of the folder path, including the file name, is 1024 characters.
File upload size: A file upload size cannot exceed 5 GiB (5368709120 bytes) for contract-owned buckets and 4,65 GiB (5000000000 bytes) for user-owned buckets. If you have a single file exceeding this limit, you can bypass it using multi-part uploads. CLI tools such as AWS CLI and graphical tools such as Cyberduck automatically handle larger files by breaking them into parts during uploading.
Bandwidth: Each connection is theoretically capped at approximately 10 G per region. However, remember that this is a shared environment. Based on our operational data, achieving peak loads up to 2x7 G is feasible by leveraging parallel connections. However, this is on a best-effort basis and without any guaranteed Service Level Agreement (SLA).