2025-04-07
Updated the following content:
diff --git a/docs/obs/s3api/en-us_topic_0125560305.html b/docs/obs/s3api/en-us_topic_0125560305.html index 51eb31243..9207ed5a7 100644 --- a/docs/obs/s3api/en-us_topic_0125560305.html +++ b/docs/obs/s3api/en-us_topic_0125560305.html @@ -8,7 +8,7 @@
In multiple regions scenarios, if user A creates a bucket, deletes the bucket later, and immediately creates a bucket with the same name in different regions, the system will respond 409. If user A creates a bucket with the same name in different regions 30 minutes later, the system will respond 200.
If a 5xx error is returned from the server or the request times out during bucket creation, the system takes about 10 minutes to make bucket information consistent. During the process, bucket information is inaccurate.
Storage Class
Users are allowed to create buckets of different storage classes. The x-default-storage-class header in a bucket creation request specifies the default storage class for a bucket. The storage class of the objects in a bucket is the same as that of the bucket. There are three storage classes: STANDARD (OBS Standard), STANDARD_IA (OBS Warm), and GLACIER (OBS Cold). If this header is not in the request, the storage class of the bucket created is OBS Standard. When users upload an object to a bucket, if they do not set the storage class of the object (see PUT Object), the object will use the default storage class of the bucket.
+Storage Class
Users are allowed to create buckets of different storage classes. The x-default-storage-class header in a bucket creation request specifies the default storage class for a bucket. There are three storage classes: STANDARD (OBS Standard), STANDARD_IA (OBS Warm), and GLACIER (OBS Cold). If this header is not in the request, the storage class of the bucket created is OBS Standard. When users upload an object to a bucket, if they do not set the storage class of the object (see PUT Object), the object will use the default storage class of the bucket.
Request Syntax
PUT / HTTP/1.1 User-Agent: agent diff --git a/docs/obs/s3api/en-us_topic_0125560403.html b/docs/obs/s3api/en-us_topic_0125560403.html index 56565c8c8..b620f7375 100644 --- a/docs/obs/s3api/en-us_topic_0125560403.html +++ b/docs/obs/s3api/en-us_topic_0125560403.html @@ -59,7 +59,7 @@ Content-Length: 0
Error Responses
No special error responses are returned. For details about error responses, see Table 1.
Sample Request
PUT / HTTP/1.1 +Sample Request
PUT /?storagePolicy HTTP/1.1 User-Agent: Jakarta Commons-HttpClient/3.1 Host: bucketname.obs.example.com Accept: */* diff --git a/docs/obs/s3api/en-us_topic_0125560423.html b/docs/obs/s3api/en-us_topic_0125560423.html index b4d1ce5f9..34aa7a1c8 100644 --- a/docs/obs/s3api/en-us_topic_0125560423.html +++ b/docs/obs/s3api/en-us_topic_0125560423.html @@ -2,7 +2,7 @@PUT Bucket lifecycle
OBS supports periodic transition and deletion of objects in a bucket based on a specified rule. This is implemented in lifecycle configuration. After the bucket lifecycle is set, OBS automatically deletes objects at the time specified in this operation. This operation can be used to delete:
-+
- Periodically uploaded files: Some periodically uploaded files need to be retained for only one week or one month.
- Documents that are seldom accessed after a certain period of time. These documents may be archived for another period of time and be deleted then.
- The minimum time for the transition of the bucket storage to Warm or to Cold can be configured. The value ranges from 24 to 8640.
- Periodically uploaded files: Some periodically uploaded files need to be retained for only one week or one month.
- Documents that are seldom accessed after a certain period of time. These documents may be archived for another period of time and be deleted then.
This operation is used to create or update the lifecycle configuration of a bucket.
Only users granted the s3:PutLifecycleConfiguration permission can create or update the bucket lifecycle configuration. By default, only the bucket owner can set the bucket lifecycle configuration. The bucket owner can allow other users to set the bucket lifecycle configuration by granting them the permission.
The lifecycle configuration supports periodic deletion and transition of objects. If you want to prevent a user from deleting and transitioning objects, disable the following permissions:
@@ -21,7 +21,7 @@ Expect: expect <LifecycleConfiguration> <Rule> <ID>id</ID> - <Prefix>prefix</Prefix> + <Prefix>prefix</Prefix> <Status>status</Status> <Expiration> <Days>365</Days> @@ -129,7 +129,7 @@ Expect: expectChildren: Date or Days, StorageClass
Ancestor: Rule
Mandatory if NoncurrentVersionTransition, Expiration, and NoncurrentVersionExpiration are absent.
+Mandatory if NoncurrentVersionTransition, Expiration, AbortIncompleteMultipartUpload, and NoncurrentVersionExpiration are absent.