Skip to content

Commit d917f88

Browse files
authored
Update guide.en-ie.md
additional infos on transition delays
1 parent 22ae330 commit d917f88

File tree

1 file changed

+4
-4
lines changed
  • pages/storage_and_backup/object_storage/s3_bucket_lifecycle

1 file changed

+4
-4
lines changed

pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-ie.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -375,8 +375,8 @@ OVHcloud Object Storage will prevent any transition to any storage tier for obje
375375
### Minimum transition delay
376376

377377
The minimum duration for transition rules is **30 days** i.e your lifecycle configuration will not be valid and you will get an error if the number of days for your transition rule is less than 30 days. In practice, it means that the lifecycle feature will only consider objects older than **30 days**.
378-
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard after a certain amount of time and then from Standard to Standard Infrequent Access after another amount of time. That means:
379-
- your object can only be transitioned to Standard after 30 days
378+
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard storage tier after a certain amount of time and then from Standard to Standard Infrequent Access storage tier after another amount of time. That means:
379+
- your object can only be transitioned from High Performance to Standard after 30 days
380380
- your object can only be transitioned from Standard to Standard Infrequent Access after 60 days (30 days after the previous transition)
381381

382382
### Expiration vs transitions
@@ -474,7 +474,7 @@ In this scenario, suppose you upload an object with multiple versions:
474474
If the current date is 2024-10-23:
475475

476476
- v5 will be transitioned 30 days after 2024-10-23
477-
- v1 will be transitioned since it has been a noncurrent version for 5 days already
477+
- v1 will be transitioned 30 days after its creation i.e 2024-10-18
478478

479479
```json
480480
{
@@ -491,7 +491,7 @@ If the current date is 2024-10-23:
491491
],
492492
"NoncurrentVersionTransitions": [
493493
{
494-
"NoncurrentDays": 5,
494+
"NoncurrentDays": 30,
495495
"StorageClass": "STANDARD"
496496
}
497497
]

0 commit comments

Comments
 (0)