9 min read

Learning Objectives

By the end of this module, you will be able to:

  • Choose between contract-owned and user-owned buckets by region, access model and the features each type supports
  • Design tamper-evident retention with Object Lock and cost control with lifecycle rules, knowing which settings are final at bucket creation
  • Plan cross-region copies within the replication rules, including the limits for locked and contract-owned buckets
  • Assign IONOS Cloud Object Storage its roles in the architecture: audit archive, backup target, artifact and dataset store, and dead-letter destination
  • Create a bucket with Object Lock and a lifecycle rule in the Data Center Designer (DCD)

Unit 5.2: Object Storage

Introduction

Almost every later unit sends data to a bucket: the activity-log export of Unit 2.3, the flow logs of Unit 3.2, the database backups of Unit 5.3, the event archive of Unit 5.6. IONOS Cloud Object Storage is the one store that every tier reaches, so its design choices, made once, shape all of those flows.

Two of those choices cannot be revisited. The bucket type fixes the region and the feature set, and Object Lock can only be enabled when the bucket is created. This unit designs both and ends by building FinCorp's audit archive bucket in the DCD.

1. The Model: Flat Namespace, Keys, Two Bucket Types

1.1 How Access Works

Object Storage adheres to the S3 protocol, so S3 tools and applications built for S3-compatible platforms work against it. Data is held as objects and buckets in a flat environment: a "folder" is a key prefix, not a directory. Objects carry metadata and a unique identifier, and the service stores them with erasure coding, which splits data into fragments with redundant pieces across a set of servers.

Authentication uses a pair of keys, an Access Key and a Secret Key, which you generate manually in the DCD or through the Object Storage Management API. A user can create a maximum of five keys, for different S3 applications. A user who is neither the contract owner nor an administrator needs membership in a group with the Use Object Storage privilege. Treat keys like any service credential: one per application, held by a service account (Unit 2.2), deactivated when the application is retired.

1.2 Contract-Owned or User-Owned

The bucket type decides who owns the bucket and where it can live. Contract-owned buckets use the contract owner as the bucket owner, every user in the contract sees the bucket list, and only the contract owner or an administrator grants access to content. User-owned buckets belong to the user who created them and are invisible to other users. The shift toward the contract-owned model is the primary focus of future Object Storage updates.

Contract-owned buckets are created in eu-central-4 (Frankfurt), eu-central-3 (Berlin) and us-central-1 (Lenexa), each with its own endpoint, such as s3.eu-central-4.ionoscloud.com. User-owned buckets are created in de (Frankfurt), eu-central-2 (Berlin) and eu-south-2 (Logroño). The BSI IT-Grundschutz certification for the eu-central-3 region is currently pending, which is why FinCorp's audit archive sits in eu-central-4 (Unit 2.3).

The feature sets differ:

Features Contract-owned buckets User-owned buckets
Bucket ACL Use to share access to other contracts. To share access with users from the same contract, use Bucket Policy. Use to share access between users of the contract and to other contracts.
Bucket Access Logging Not supported Supported
Bucket Replication Cross-regional bucket replication is not supported for contract-owned buckets but will be available soon. You can only replicate user-owned buckets in the contract-owned buckets region. This function is supported both through the DCD and the API. It supports replication within the same user's user-owned buckets and in contract-owned buckets. You can also replicate within the regions where user-owned buckets are supported.
Identity and Access Management (IAM) No, available in the near future. Not supported
Object Query Supported Not supported
Redirects for Static Website Hosting Supported Not supported
Free data transfer to VMs within the same region Supported Not supported
Flow logs Not supported Supported

As shown above, the choice is per workload. Contract-owned buckets suit organisation-wide data and are free to read from VMs in the same region. Flow logs, however, do not operate on contract-owned buckets, so the flow-log destination of Unit 3.2 is a user-owned bucket in de.

2. Retention and Cost: Object Lock and Lifecycle

2.1 Object Lock

Object Lock applies Write Once Read Many (WORM) protection, preventing objects from being deleted or modified for a set duration. Once a bucket is created without Object Lock, you cannot add it later. Enabling it also enables versioning, and neither can be disabled afterwards.

Two modes exist. Governance lets users with special permissions override the lock, for example to correct a mistake. Compliance enforces the lock without any override: the retention period cannot be shortened or removed, by the bucket owner or by IONOS CLOUD, until it has passed. The DCD sets a retention period of up to 365 days; longer periods, up to 100 years, are set through the API.

Two details matter for audits. A delete request on a locked object creates a delete marker instead of removing the version, and delete markers themselves are not protected. The evidence stays intact, but a listing can look empty; auditors read versions, not the current listing.

2.2 Lifecycle Rules

A lifecycle rule applies to the whole bucket or to one prefix, and supports four actions: expire current versions, permanently delete noncurrent versions, delete expired object delete markers, and delete incomplete multipart uploads. A configuration holds up to 1,000 rules, and only one rule can apply to a given prefix.

Only the Standard storage class exists, so lifecycle rules cannot move objects to a cheaper tier: cost control means deletion. On a locked bucket, noncurrent versions cannot be deleted before their retention period ends, so the lifecycle rule and the lock work together: the lock guarantees the minimum, the rule removes data after it.

3. Cross-Region Copies and the Roles of a Bucket

3.1 Replication Rules

Replication needs versioning on both the source and the destination bucket, copies only objects uploaded after it is enabled, and does not chain: an object that is itself a replica is not replicated again. Replication traffic, including cross-region traffic, is not counted towards data usage.

Three limits drive the design. Cross-regional replication is not supported for contract-owned buckets. A bucket with Object Lock cannot be a replication source, though it can be a destination. And a deletion that names an object version deletes it in the source only. For FinCorp's locked audit archive, a Berlin copy therefore comes from the exporter itself, which writes each daily file to a second bucket, not from bucket replication.

3.2 The Four Roles

Role Bucket design Unit
Audit archive Contract-owned, Object Lock in Compliance mode, lifecycle deletion after retention 2.3, this unit
Backup target Database and In-Memory DB backup locations; a Backup Service storage target 5.3, 5.5, 5.7
Artifact and dataset store Contract-owned in the compute region, so VMs read it without transfer charges 6.5
Dead-letter destination Separate prefix per topic, lifecycle expiry after the investigation window 5.6

DCD Implementation Walkthrough

You will create FinCorp's audit archive bucket in Frankfurt with Object Lock in Compliance mode, then add the lifecycle rule that removes old versions once their retention has passed. This realises the archive role from Section 3.2.

Prerequisites: a contract owner or administrator account, since only they can create contract-owned buckets; at least one active access key; the retention period signed off by FinCorp's risk office.

Build goal: Create a bucket, set Object Lock and a lifecycle policy.

Steps (in the Data Center Designer):

  1. Go to Menu > Backup & Storage > Object Storage. In the Buckets tab, select Create bucket.
  2. In Bucket region, select eu-central-4.
  3. Enter the Bucket name fc-audit-archive-fra. If a bucket with the same name already exists in IONOS Cloud Object Storage, the bucket is not created, so prefix names with your organisation.
  4. Select Enable Object Lock. This is the only moment to do so.
  5. Select Compliance mode and enter a Retention period in days. The DCD accepts up to 365 days; set the signed-off multi-year period through the API after creation (see the snippet below).
  6. Select Create bucket. Versioning is now on and cannot be suspended.
  7. Open the bucket, select Bucket settings, and under Data management > Lifecycle select Add a rule.
  8. Enter the Lifecycle Rule name expire-after-retention and set the Rule Scope to the prefix activity-logs/. Select Expire current versions with a day count equal to the retention period, Permanently delete noncurrent versions of objects with a short grace period after that, and Delete incomplete multipart uploads after a few days.
  9. Select Save.

A longer retention period is set through the S3 API. The architectural point is that the mode and the default retention are a bucket-level rule that applies to newly uploaded objects:

aws s3api put-object-lock-configuration \
 --bucket fc-audit-archive-fra \
 --object-lock-configuration '{ "ObjectLockEnabled": "Enabled", "Rule": { "DefaultRetention": { "Mode": "COMPLIANCE", "Days": <retention-days> }}}' \
 --endpoint-url https://s3.eu-central-4.ionoscloud.com

Common mistakes:

  • Creating the bucket first and planning to "add the lock later". It cannot be added.
  • Testing Compliance mode with a long retention period. Test objects stay until the period ends; test with Governance mode and a short period in a separate bucket.
  • Expecting a lifecycle rule to move data to a cheaper class. Only Standard exists; lifecycle deletes.
  • Choosing a contract-owned bucket as a flow-log destination. Flow logs need a user-owned bucket.
  • Planning bucket replication out of the locked archive. A locked bucket can receive replicas but cannot be a source.

Summary

Object Storage is the store every tier writes to, so decide its structure up front. The bucket type fixes the region and the features, Object Lock is a creation-time decision with versioning attached, and lifecycle rules control cost only by deleting. Replication is free but bounded: no cross-region replication for contract-owned buckets and no locked source buckets, so a locked archive gets its second copy from the writer.

Key Points:

  • Contract-owned buckets live in eu-central-4, eu-central-3 and us-central-1; user-owned buckets in de, eu-central-2 and eu-south-2.
  • Object Lock must be enabled at bucket creation; Compliance mode cannot be shortened by anyone.
  • The DCD sets retention up to 365 days; the API sets longer periods.
  • Lifecycle rules expire and delete; there is no storage class transition.
  • Flow logs and bucket access logging need user-owned buckets.

Important Terminology:

  • Contract-owned bucket: a bucket owned by the contract owner, visible to all contract users, with access granted by an owner or administrator.
  • Compliance mode: the Object Lock mode in which no one can shorten or remove the retention period.
  • Delete marker: the placeholder a delete request creates on a versioned bucket instead of removing the object version.