检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Server-side encryption: You can use server-side encryption to encrypt data uploaded to OBS buckets. WORM: You can configure WORM for your bucket to prevent objects in the bucket from being deleted or tampered with within a specified period.
Server-side encryption: You can use server-side encryption to encrypt data uploaded to OBS buckets. WORM: You can configure WORM for your bucket to prevent objects in the bucket from being deleted or tampered with within a specified period.
Server-side encryption: You can use server-side encryption to encrypt data uploaded to OBS buckets. WORM: You can configure WORM for your bucket to prevent objects in the bucket from being deleted or tampered with within a specified period.
Server-side encryption: You can use server-side encryption to encrypt data uploaded to OBS buckets. WORM: You can configure WORM for your bucket to prevent objects in the bucket from being deleted or tampered with within a specified period.
CtrRSACipherGenerator is inherited from CTRCipherGenerator but only requires you to provide an RSA public or private key to encrypt or decrypt the randomly generated data key. CTRCipherGenerator requires only one data key. This key is used to encrypt all objects.
You can encrypt bucket inventory files in the SSE-KMS mode. You can set the frequency (daily or weekly) for generating bucket inventory files. You can also specify a bucket to store the generated bucket inventory files.
OBS then uses the key and algorithm you provided to encrypt or decrypt your object. OBS does not store your encryption keys. If you lose them, you lose the objects. For details, see Server-Side Encryption (SSE-C).
For security purposes, encrypt your AK/SK and store them in the configuration file or environment variables. In this example, the AK/SK are stored in environment variables for identity authentication.
All Supported Supported Server-side encryption To enhance data security, OBS uses server-side encryption to encrypt data before storing it. The encryption methods include SSE-KMS, SSE-OBS, and SSE-C. See Function Overview.
For security purposes, encrypt your AK and SK and store them in the configuration file or environment variables. # In this example, the AK and SK are stored in environment variables for identity authentication.
The key shared by other users will be used to encrypt your objects. For details about how to obtain a shared key ID, see Viewing a CMK. NOTE: A shared key from a project or a subproject can be configured here.
The key shared by other users will be used to encrypt your objects. For details about how to obtain a shared key ID, see Viewing a CMK. NOTE: A shared key from a project or a subproject can be configured here.
The key shared by other users will be used to encrypt your objects. For details about how to obtain a shared key ID, see Viewing a CMK. NOTE: A shared key from a project or a subproject can be configured here.
The key shared by other users will be used to encrypt your objects. For details about how to obtain a shared key ID, see Viewing a CMK. NOTE: A shared key from a project or a subproject can be configured here.
Value range: AES256 (AES256 encryption algorithm) Default value: None ssec_customer_key char * No Explanation: Indicates the key used to encrypt an object. Restrictions: The header is used only in SSE-C mode.
For security purposes, encrypt your AK and SK and store them in the configuration file or environment variables. // In this example, the AK and SK are stored in environment variables for identity authentication.
For security purposes, encrypt your AK and SK and store them in the configuration file or environment variables. // In this example, the AK and SK are stored in environment variables for identity authentication.
For security purposes, encrypt your AK and SK and store them in the configuration file or environment variables. In this example, the AK and SK are stored in environment variables for identity authentication.
For security purposes, encrypt your AK and SK and store them in the configuration file or environment variables. // In this example, the AK and SK are stored in environment variables for identity authentication.
Value range: AES256 (AES256 encryption algorithm) Default value: None ssec_customer_key char * No Explanation: Indicates the key used to encrypt an object. Restrictions: The header is used only in SSE-C mode.