Skip to content

Commit fb8045a

Browse files
authored
Update EN guide.en-gb.md
Adding new definitions to: - minimum storage duration - retrieval fee - lifecycle management support
1 parent 8688789 commit fb8045a

File tree

1 file changed

+13
-0
lines changed
  • pages/storage_and_backup/object_storage/s3_choosing_the_right_storage_class_for_your_needs

1 file changed

+13
-0
lines changed

pages/storage_and_backup/object_storage/s3_choosing_the_right_storage_class_for_your_needs/guide.en-gb.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,19 @@ This offer is suitable for the following use cases: long-term storage, backups,
4242

4343
More details about available regions [here](/pages/storage_and_backup/object_storage/s3_location).
4444

45+
### Additional details
46+
#### Minimum storage duration
47+
It refers to the **minimum amount of time that an object must be stored in a particular storage class**. In case of early deletion, using *delete-object* requests, a pro-rated fee equal to the remaining days is applied. Be careful with non-versioned buckets, if the object is overwritten, this will be considered as a deletion of the current object version and the pro-rated fee will be applied too.
48+
For example, for the Infrequent Access class, the minimum storage time is 730 hours (30 days). If an object is deleted during this period, an additional charge will be applied and calculated using the following formula: [730h - # of hours of storage of the object] x price per hour of storage class.
49+
50+
#### Retrieval fee
51+
It refers to a **charge that is applied when you retrieve or access data that is stored in a particular storage class**. The retrieval fee is calculated based on the amount of data retrieved (per GiB retrieved).
52+
For the Infrequent Access class, only *get-object* requests are considered as retrieval fee.
53+
For our Cold Archive class, only *restore* requests are considered as retrieval fee.
54+
55+
#### Lifecycle management support
56+
It refers to the ability to **automatically manage the storage lifecycle of your objects**, such as transitioning them from one storage class to another, based on predefined rules and policies. This allows you to optimize storage costs and simplify data management. Object-level granularity is required because it allows you to manage at the individual object level. **Lifecycle transition requests are free of charge.**
57+
More details about lifecycle management [here](/pages/storage_and_backup/object_storage/s3_bucket_lifecycle).
4558

4659
## OpenStack SWIFT Object Storage tiers
4760

0 commit comments

Comments
 (0)