Using Customer-Managed Encryption Keys with Cloud Storage and Cloud KMS Reviews

As expected

Peter C. · Reviewed about 5 years ago

Brandon S. · Reviewed about 5 years ago

Ananth R. · Reviewed about 5 years ago

Christophe L. · Reviewed about 5 years ago

Roman K. · Reviewed about 5 years ago

Thanks!

Natchanon A. · Reviewed about 5 years ago

E E. · Reviewed about 5 years ago

Manuel A. · Reviewed about 5 years ago

Manuel H. · Reviewed about 5 years ago

Mathijs M. · Reviewed about 5 years ago

A. A. · Reviewed about 5 years ago

Praveen M. · Reviewed about 5 years ago

Krzysztof K. · Reviewed about 5 years ago

Bartosz S. · Reviewed about 5 years ago

Good

Ganesh N. · Reviewed about 5 years ago

R C. · Reviewed about 5 years ago

Ashish H. · Reviewed about 5 years ago

Arianit S. · Reviewed about 5 years ago

Dario C. · Reviewed about 5 years ago

Brigitte L. · Reviewed about 5 years ago

Please consider adding task for re-encrypting file with new/rotated CMEK, similar to "gsutil rewrite -k gs://$BUCKET_NAME/OBJECT_NAME" CSEK

Leonid L. · Reviewed about 5 years ago

This command didn't work: "https://cloudkms.googleapis.com/v1/projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings/$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME:encrypt" \ -d "{\"WWFra28gV2Fra28gYW5kIERvdA==\":\"WWFra28gV2Fra28gYW5kIERvdA==\"}" \ -H "Authorization:Bearer $(gcloud auth application-default \ print-access-token)" \ -H "Content-Type: application/json" I replaced the "plaintext" variable with the base 64 code as instructed

Seth H. · Reviewed about 5 years ago

LTI S. · Reviewed about 5 years ago

Ce X. · Reviewed about 5 years ago

Ravi T. · Reviewed about 5 years ago