检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
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.
If a versioned object is encrypted with SSE-KMS, the ACL configured for it is not in effect in the cross-tenant case. You can set an access control policy when uploading a versioned object or call an ACL API to modify or obtain the ACL of an existing object.
Objects created by the upload and copy operations are assigned 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. Size number Explanation: Object size, in bytes.
The object cannot be decrypted due to incorrect encryption header carried when downloading the SSE-C encrypted object.
Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object. SseKms string Explanation: SSE-KMS is used for encrypting objects on the server side. SseKmsKey string Explanation: ID of the KMS master key when SSE-KMS is used.
Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object. SseKms string Explanation: SSE-KMS is used for encrypting objects on the server side. SseKmsKey string Explanation: ID of the KMS master key when SSE-KMS is used.
Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object. SseKms string Explanation: SSE-KMS is used for encrypting objects on the server side. SseKmsKey string Explanation: ID of the KMS master key when SSE-KMS is used.
However, if a shared key from a subproject is specified, the owner of the shared key cannot access objects encrypted with that key, but the bucket owner can. Selecting SSE-OBS for Encryption Method will use the keys created and managed by OBS for encryption.
However, if a shared key from a subproject is specified, the owner of the shared key cannot access objects encrypted with that key, but the bucket owner can. Selecting SSE-OBS for Encryption Method will use the keys created and managed by OBS for encryption.
However, if a shared key from a subproject is specified, the owner of the shared key cannot access objects encrypted with that key, but the bucket owner can. Selecting SSE-OBS for Encryption Method will use the keys created and managed by OBS for encryption.
However, if a shared key from a subproject is specified, the owner of the shared key cannot access objects encrypted with that key, but the bucket owner can. Selecting SSE-OBS for Encryption Method will use the keys created and managed by OBS for encryption.
If an object is encrypted with SSE-KMS, the ACL configured for it is not in effect in the cross-tenant case. For more information, see ACLs. If you have any questions during development, post them on the Issues page of GitHub.
Objects are encrypted using SSE-KMS on the server side. Value range: kms. For details, see Table 8. Default value: None sseAlgorithm SSEAlgorithmEnum No Explanation: Encryption algorithm. Restrictions: Only KMS is supported. Value range: See Table 9.
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: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object.
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. Default value: None expiration const char * No Explanation: Expiration details of the object.
Restrictions: If an object is encrypted using server-side encryption, the ETag is not the MD5 value of the object. Value range: None Default value: None callback_data void * Yes Explanation: The pointer to the custom callback data.
Function This API configures server-side encryption for objects, so that they will be encrypted or decrypted when you upload them to or download them from a bucket. The encryption and decryption happen on the server side.
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.
Code Example: Downloading an Object Encrypted Using SSE-C This example uses HttpMethodEnum.GET to download an object encrypted using SSE-C.
