Ctrlk
HomeLog InSign UpSend Feedback
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Lifecycle

Lifecycle Configuration of a Bucket

GetBucketLifecycle

get
/{Bucket}?lifecycle

Returns the lifecycle configuration for the specified object storage bucket.

Permissions

You must be the contract owner or an administrator to perform this operation. If not, they can grant you permission to perform the s3:GetLifecycleConfiguration operation using Bucket Policy.

Authorizations
AuthorizationstringRequired

IONOS CLOUD Object Storage API requests are authenticated using the AWS signature. The IONOS CLOUD Object Storage API authenticates users using a customized HTTP scheme based on a keyed-HMAC (Hash Message Authentication Code). The process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.

In the Authorization tab for a request, select AWS Signature from the Type dropdown list. Specify where Postman should append your authorization data using the Add authorization data to drop-down menu.

  • If you select Request Headers, Postman populates the Headers tab with Authorization and X-Amz- prefixed fields.

  • If you select Request URL, Postman populates the Params tab with authentication details prefixed with X-Amz-.

Note: The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.

  • For Access Key, enter your access key directly in the fields or through variables for added security.

  • For Secret Key, enter your secret key directly in the fields or through variables for added security.

Advanced fields are optional, but Postman will attempt to generate them automatically if necessary.

  • For AWS Region, enter one of the regions (eu-central-3) where your bucket is hosted.

  • For Service Name, enter s3. The name of the service that receives the requests.

  • For Session Token, leave the field blank. This is only required when temporary security credentials are used.

Path parameters
Bucketstring · min: 3 · max: 63Required

The bucket name.

Example: my-bucket
Query parameters
lifecycleboolean · enumRequiredPossible values:
Responses
200

Successful operation

application/xml
get/{Bucket}?lifecycle
GET /{Bucket}?lifecycle?lifecycle=true HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Accept: */*

<?xml version="1.0" encoding="UTF-8"?>
<LifecycleConfiguration>
<Rule>
    <ID>Delete logs after 30 days with size between 104857600 and 1073741824 bytes</ID>
    <Filter>
        <ObjectSizeGreaterThan>104857600</ObjectSizeGreaterThan>
        <ObjectSizeLessThan>1073741824</ObjectSizeLessThan>
        <Prefix>logs/</Prefix>
    </Filter>
    <Status>Enabled</Status>
    <Expiration>
    <Days>30</Days>
    </Expiration>
</Rule>
<Rule>
    <ID>Delete objects 60 days after becoming non-current for bucket with Versioning enabled</ID>
    <Filter>
        <Prefix>temp/</Prefix>
    </Filter>
    <Status>Enabled</Status>
    <NoncurrentVersionExpiration>
        <NoncurrentDays>60</NoncurrentDays>
    </NoncurrentVersionExpiration>
</Rule>
<Rule>
    <ID>Remove incomplete multipart uploads after 5 days</ID>
    <Filter>
        <Prefix />
    </Filter>
    <Status>Enabled</Status>
    <AbortIncompleteMultipartUpload>
        <DaysAfterInitiation>5</DaysAfterInitiation>
    </AbortIncompleteMultipartUpload>
</Rule>
</LifecycleConfiguration>

PutBucketLifecycle

put
/{Bucket}?lifecycle

Creates a new lifecycle configuration for a specified bucket, or replaces an existing configuration.

This lifecycle configuration allows automatic management of the objects within the bucket. Typical actions can include the deletion of objects after a certain period or deletion of non-current versions of objects.

Permissions

You must be the contract owner or an administrator to perform this operation. If not, they can grant you permission to perform the s3:PutLifecycleConfiguration operation using Bucket Policy.

S3 API Compatibility

  • The NewerNoncurrentVersions setting is not supported for the NoncurrentVersionExpiration option.

  • The Transition and the NoncurrentVersionTransition options are omitted as only the STANDARD storage class is currenly supported.

Authorizations
AuthorizationstringRequired

IONOS CLOUD Object Storage API requests are authenticated using the AWS signature. The IONOS CLOUD Object Storage API authenticates users using a customized HTTP scheme based on a keyed-HMAC (Hash Message Authentication Code). The process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.

In the Authorization tab for a request, select AWS Signature from the Type dropdown list. Specify where Postman should append your authorization data using the Add authorization data to drop-down menu.

  • If you select Request Headers, Postman populates the Headers tab with Authorization and X-Amz- prefixed fields.

  • If you select Request URL, Postman populates the Params tab with authentication details prefixed with X-Amz-.

Note: The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.

  • For Access Key, enter your access key directly in the fields or through variables for added security.

  • For Secret Key, enter your secret key directly in the fields or through variables for added security.

Advanced fields are optional, but Postman will attempt to generate them automatically if necessary.

  • For AWS Region, enter one of the regions (eu-central-3) where your bucket is hosted.

  • For Service Name, enter s3. The name of the service that receives the requests.

  • For Session Token, leave the field blank. This is only required when temporary security credentials are used.

Path parameters
Bucketstring · min: 3 · max: 63Required

The bucket name.

Example: my-bucket
Query parameters
lifecycleboolean · enumRequiredPossible values:
Header parameters
Content-MD5stringRequired

The base64 encoded MD5 digest of the message (without the headers) according to RFC 1864.

Body
Responses
200

Successful operation

application/xml
put/{Bucket}?lifecycle
PUT /{Bucket}?lifecycle?lifecycle=true HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Content-MD5: text
Content-Type: application/xml
Accept: */*
Content-Length: 1094

"<?xml version="1.0" encoding="UTF-8"?>
<LifecycleConfiguration>
<Rule>
    <ID>Delete logs after 30 days with size between 104857600 and 1073741824 bytes</ID>
    <Filter>
        <ObjectSizeGreaterThan>104857600</ObjectSizeGreaterThan>
        <ObjectSizeLessThan>1073741824</ObjectSizeLessThan>
        <Prefix>logs/</Prefix>
    </Filter>
    <Status>Enabled</Status>
    <Expiration>
    <Days>30</Days>
    </Expiration>
</Rule>
<Rule>
    <ID>Delete objects 60 days after becoming non-current for bucket with Versioning enabled</ID>
    <Filter>
        <Prefix>temp/</Prefix>
    </Filter>
    <Status>Enabled</Status>
    <NoncurrentVersionExpiration>
        <NoncurrentDays>60</NoncurrentDays>
    </NoncurrentVersionExpiration>
</Rule>
<Rule>
    <ID>Remove incomplete multipart uploads after 5 days</ID>
    <Filter>
        <Prefix />
    </Filter>
    <Status>Enabled</Status>
    <AbortIncompleteMultipartUpload>
        <DaysAfterInitiation>5</DaysAfterInitiation>
    </AbortIncompleteMultipartUpload>
</Rule>
</LifecycleConfiguration>
"
No content

DeleteBucketLifecycle

delete
/{Bucket}?lifecycle

Deletes the lifecycle configuration from the specified bucket. As a result, objects within the bucket will neither expire nor be automatically deleted based on any rules from the deleted configuration.

Permissions

You must be the contract owner or an administrator to perform this operation. If not, they can grant you permission to perform the s3:PutLifecycleConfiguration operation using Bucket Policy.

Note: A brief delay may occur before the lifecycle configuration deletion is fully propagated across all IONOS CLOUD Object Storage systems. During this time, lifecycle rules may remain temporarily active.

Authorizations
AuthorizationstringRequired

IONOS CLOUD Object Storage API requests are authenticated using the AWS signature. The IONOS CLOUD Object Storage API authenticates users using a customized HTTP scheme based on a keyed-HMAC (Hash Message Authentication Code). The process of generating the proper Authorization header is somewhat involved. We recommend that you make use of a tool such as Postman.

In the Authorization tab for a request, select AWS Signature from the Type dropdown list. Specify where Postman should append your authorization data using the Add authorization data to drop-down menu.

  • If you select Request Headers, Postman populates the Headers tab with Authorization and X-Amz- prefixed fields.

  • If you select Request URL, Postman populates the Params tab with authentication details prefixed with X-Amz-.

Note: The parameters listed below contain confidential information. We recommend using variables to keep this data secure while working in a collaborative environment.

  • For Access Key, enter your access key directly in the fields or through variables for added security.

  • For Secret Key, enter your secret key directly in the fields or through variables for added security.

Advanced fields are optional, but Postman will attempt to generate them automatically if necessary.

  • For AWS Region, enter one of the regions (eu-central-3) where your bucket is hosted.

  • For Service Name, enter s3. The name of the service that receives the requests.

  • For Session Token, leave the field blank. This is only required when temporary security credentials are used.

Path parameters
Bucketstring · min: 3 · max: 63Required

The bucket name.

Example: my-bucket
Query parameters
lifecycleboolean · enumRequiredPossible values:
Responses
204

Successful operation

application/xml
delete/{Bucket}?lifecycle
DELETE /{Bucket}?lifecycle?lifecycle=true HTTP/1.1
Host: s3.eu-central-1.ionoscloud.com
Authorization: YOUR_API_KEY
Accept: */*
204

Successful operation

No content
PreviousEncryption
NextLogging

Last updated

Was this helpful?