An optional parameter to set the Customer-Supplied Encryption key for rewrite source object.
Application developers can generate their own encryption keys to protect the data in GCS. This is known as a Customer-Supplied Encryption key (CSEK). If the application provides a CSEK, GCS does not retain the key. The object data, the object CRC32 checksum, and its MD5 hash (if applicable) are all encrypted with this key, and the key is required to read any of these elements back.
Care must be taken to save and protect these keys, if lost, the data is not recoverable. Also, applications should avoid generating predictable keys, as this weakens the encryption.
This option is used only in rewrite operations and it defines the key used for the source object.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-22 UTC."],[[["This webpage provides documentation for the `SourceEncryptionKey` structure within the Google Cloud Storage C++ client library, covering versions from 2.11.0 up to the latest release candidate 2.37.0-rc."],["`SourceEncryptionKey` is an optional parameter used in rewrite operations to specify a Customer-Supplied Encryption Key (CSEK) for the source object in Google Cloud Storage."],["Customer-Supplied Encryption Keys allow users to encrypt data in GCS using their own keys, which are not retained by GCS and are necessary to read the encrypted data."],["The page details how to create a `SourceEncryptionKey` using either a raw binary key or a base64-encoded key, both of which must represent a 32-byte key when decoded."],["The documentation emphasizes the importance of securely managing CSEKs, as data encrypted with a lost key cannot be recovered, and recommends avoiding predictable key generation to ensure strong encryption."]]],[]]
