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

Gabriel M. · Reviewed about 5 years ago

Marcos C. · Reviewed about 5 years ago

.

Felipe d. · Reviewed about 5 years ago

Eduardo A. · Reviewed about 5 years ago

Hélène S. · Reviewed about 5 years ago

Kayode O. · Reviewed about 5 years ago

Hiren P. · Reviewed about 5 years ago

Mario M. · Reviewed about 5 years ago

Desmond L. · Reviewed about 5 years ago

Samuel R. · Reviewed about 5 years ago

Trent G. · Reviewed about 5 years ago

Shelly J. · Reviewed about 5 years ago

Mohamad S. · Reviewed about 5 years ago

:)

Tan S. · Reviewed about 5 years ago

worked this time

Steve M. · Reviewed about 5 years ago

Mariusz D. · Reviewed about 5 years ago

Chetan M. · Reviewed about 5 years ago

Chetan M. · Reviewed about 5 years ago

Liza Y. · Reviewed about 5 years ago

Learned new knowledge today.

Noraschid G. · Reviewed about 5 years ago

John M. · Reviewed about 5 years ago

Sathish K. · Reviewed about 5 years ago

Eric E. · Reviewed about 5 years ago

Task 3 step 1 returns error Code as written in instructions- gsutil kms encryption -k \ projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings\ /$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME \ gs://$DEVSHELL_PROJECT_ID-kms Error returned - CommandException: Invalid KMS key name: "projects/qwiklabs-gcp-01-3de2582dec6a/locations/us/keyRings//cryptoKeys/". KMS keys should follow the format "projects/<project-id>/locations/<location>/keyRings/<keyring>/cryptoKeys/<key-name>" Corrected code - gsutil kms encryption -k projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings/lab-keyring/cryptoKeys/labkey-1 gs://$DEVSHELL_PROJECT_ID-kms

Aaron H. · Reviewed about 5 years ago

Ankit D. · Reviewed about 5 years ago