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

Rachel D. · Reviewed over 2 years ago

Jauhar K. · Reviewed over 2 years ago

One misstep I corrected never allowed me to mark done (Task 4)

Tomoo W. · Reviewed over 2 years ago

Jefferson K. · Reviewed over 2 years ago

Satish R. · Reviewed over 2 years ago

Nobuyuki S. · Reviewed over 2 years ago

Raymond B. · Reviewed over 2 years ago

Edgar Alan R. · Reviewed over 2 years ago

Afendi O. · Reviewed over 2 years ago

Linus T. · Reviewed over 2 years ago

Patrick C. · Reviewed over 2 years ago

Gianesh V. · Reviewed over 2 years ago

Paweł G. · Reviewed over 2 years ago

Steven O. · Reviewed over 2 years ago

Martin Emilio R. · Reviewed over 2 years ago

Edward G. · Reviewed over 2 years ago

Arturo F. · Reviewed over 2 years ago

Cambiar punto 8 por curl -v \ "https://cloudkms.googleapis.com/v1/projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings/$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME:decrypt" \ -d "{\"ciphertext\":\"$(cat data1.encrypted)\"}" \ -H "Authorization:Bearer $(gcloud auth application-default \ print-access-token)" \ -H "Content-Type:application/json" \ | jq .plaintext -r | base64 -d > data1.decrypted

Carlos G. · Reviewed over 2 years ago

Gonzalo S. · Reviewed over 2 years ago

Nagamanikanta Sai C. · Reviewed over 2 years ago

Hector G. · Reviewed over 2 years ago

Brian W. · Reviewed over 2 years ago

Jimmy B. · Reviewed over 2 years ago

oscar r. · Reviewed over 2 years ago

Javier A. · Reviewed over 2 years ago