Examples of using Lifecycle configuration in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
When Should I Use Lifecycle Configuration?
A lifecycle configuration can have up to 1,000 rules.
Consider the following example lifecycle configuration.
To delete the lifecycle configuration use the delete-bucket-lifecycle AWS CLI command as follows.
This delay can also occur when you delete a lifecycle configuration.
You specify a lifecycle configuration as XML, consisting of one or more lifecycle rules.
Amazon S3 now supports tag based filtering in lifecycle configuration.
You might specify a lifecycle configuration in which you specify overlapping prefixes, or actions.
If you want to transition objects to the GLACIER storage class,you use lifecycle configuration.
For more information, see Lifecycle Configuration Elements.
Amazon S3 supports a waterfall model for transitioning between storage class with a lifecycle configuration.
Save the following example lifecycle configuration in a file lifecycle. .
A lifecycle configuration is a set of rules that define actions that Amazon S3 applies to a group of objects.
You set object expiration by adding lifecycle configuration to a bucket.
Use the bucket's lifecycle configuration to request that Amazon S3 delete the objects.
The following put-bucket-lifecycle CLI command adds the lifecycle configuration for the specified bucket.
You can also use lifecycle configuration on a bucket to empty its content and then delete the bucket.
For more information about lifecycle rules, see Lifecycle Configuration Elements.
You can also specify lifecycle configuration on a bucket to expire objects so that Amazon S3 can delete them.
You can direct Amazon S3 tochange the storage class of objects by adding lifecycle configuration to a bucket.
When you have multiple rules in a lifecycle configuration, an object can become eligible for multiple lifecycle actions.
Lifecycle configuration Expiration action now allows you to direct Amazon S3 to remove expired object delete markers in a versioned bucket.
To stop the lifecycle action, you must remove the action from the lifecycle configuration, disable the rule, or delete the rule from the lifecycle configuration.
When you add a lifecycle configuration to a bucket, the configuration rules apply to both existing objects and objects that you add later.
This section explains how you can set lifecycle configuration on a bucket programmatically using AWS SDKs, or by using the Amazon S3 console, or the AWS CLI.
If lifecycle configuration is enabled on the source bucket, Amazon S3 puts any lifecycle actions on hold until it marks the objects status as either COMPLETED or FAILED.
Specifically for this scenario, Amazon S3 lifecycle configuration provides an Expiration action where you can request Amazon S3 to remove the expired object delete markers.
Using lifecycle configuration, you can direct Amazon S3 to abort incomplete multipart uploads if they don't complete within a specified number of days after initiation.
For example, if lifecycle configuration is enabled only on your source bucket, Amazon S3 creates delete markers for expired objects, but it does not replicate those markers.
When you add a lifecycle configuration to a bucket, there is usually some lag before a new or updated lifecycle configuration is fully propagated to all the Amazon S3 systems.