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-05-07 UTC."],[[["This page provides documentation for the `SourceEncryptionKey` struct across multiple versions, from the latest release candidate 2.37.0-rc down to version 2.11.0."],["`SourceEncryptionKey` is used to set a Customer-Supplied Encryption Key (CSEK) for the source object during rewrite operations within Google Cloud Storage (GCS)."],["CSEKs allow application developers to encrypt their data in GCS using their own keys, which are not retained by GCS."],["The documentation details two functions for creating a source encryption key: `FromBinaryKey`, which accepts a 32-byte binary key, and `FromBase64Key`, which takes a base64-encoded key that decodes to 32 bytes."],["The `prefix()` function is also documented, but its exact purpose is not detailed."]]],[]]
