检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
SSE-KMS server-side encrypted object does not support Bucket ACL/Policy for cross-tenant authorization. Parent topic: Appendix
Restrictions: The value is encrypted by MD5 and then encoded by Base64, for example, 4XvB3tbNTN+tIEVa0/fGaQ==.
Parts created by the upload and copy operations have unique ETags after being encrypted using MD5. Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object. Value range: The value must contain 32 characters.
Cross-region replication does not replicate objects encrypted using SSE-C. Constraints Bucket versions Currently, only buckets of version 3.0 support cross-region replication. To check the bucket version, go to the Overview page of the bucket on OBS Console.
Currently, encrypted ZIP packages cannot be decompressed. Federated users cannot use the online decompression function. For more information about federated users, see What Are the Relationships Between a Huawei Cloud Account, HUAWEI ID, IAM User, and Federated User?
Objects created by the upload and copy operations have unique ETags after being encrypted using MD5. Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object. Value range: The value must contain 32 characters.
Objects created by the upload and copy operations have unique ETags after being encrypted using MD5. Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object.
Bucket inventory files can be encrypted only in the SSE-KMS mode. The bucket inventory function is offered for free, but inventory files are billed for the storage space they use.
Then all objects uploaded to this bucket will be encrypted by default. See Function Overview. Not supported Supported Multi-AZ storage When creating a bucket, you can choose multi-AZ storage to store your data in multiple AZs for a higher data reliability.
Objects created by the upload and copy operations have unique ETags after being encrypted using MD5. Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object. Value range: The value must contain 32 characters.
Restrictions: The value is encrypted by MD5 and then encoded by Base64, for example, 4XvB3tbNTN+tIEVa0/fGaQ==.
Objects created by the upload and copy operations have unique ETags after being encrypted using MD5. Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object.
An uploaded object or copied object has a unique ETag after being encrypted using MD5.
The object cannot be decrypted due to incorrect encryption header carried when downloading the SSE-C encrypted object.
The object cannot be decrypted due to incorrect encryption header carried when downloading the SSE-C encrypted object.
The object cannot be decrypted due to incorrect encryption header carried when downloading the SSE-C encrypted object.
The object cannot be decrypted due to incorrect encryption header carried when downloading the SSE-C encrypted object.
The object cannot be decrypted due to incorrect encryption header carried when downloading the SSE-C encrypted object.
Objects created by the upload and copy operations have unique ETags after being encrypted using MD5. Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object. Value range: The value must contain 32 characters.
Restrictions: The value is encrypted by MD5 and then encoded by Base64, for example, 4XvB3tbNTN+tIEVa0/fGaQ==.