Using Customer-Supplied Encryption Keys with Cloud Storage Reviews

Pablo S. · Reviewed about 1 year ago

Jiye N. · Reviewed about 1 year ago

Jieqing O. · Reviewed about 1 year ago

Himanshu S. · Reviewed about 1 year ago

The lab didn't work as intended and could proceed with the creating bucket. Retring again by restarting.

manish s. · Reviewed about 1 year ago

Stevie S. · Reviewed about 1 year ago

Nadia M. · Reviewed about 1 year ago

Jose R. · Reviewed about 1 year ago

Johan C. · Reviewed about 1 year ago

승민 이. · Reviewed about 1 year ago

세은 배. · Reviewed about 1 year ago

Sara L. · Reviewed about 1 year ago

Sara L. · Reviewed about 1 year ago

Paulo L. · Reviewed about 1 year ago

Shan M. · Reviewed about 1 year ago

Sunil W. · Reviewed about 1 year ago

fidel a. · Reviewed about 1 year ago

Marius A. · Reviewed about 1 year ago

gsutil cp gs://$BUCKET_NAME/setup2.html ./ gsutil cp gs://$BUCKET_NAME/setup3.html ./ This is where the lab stops going well. CommandException: Configured encryption_key or decryption_key looked like a CMEK, but the key failed validation: Invalid KMS key name: "=Wum+PGwwGBN0Jw2l2LQvQAFOme8YzL4BZs3a4qioELo=". KMS keys should follow the format "projects/<project-id>/locations/<location>/keyRings/<keyring>/cryptoKeys/<key-name>" This message appears. And only setup3.html is downloaded. Further - worse

Aleksei K. · Reviewed about 1 year ago

Musheer A. · Reviewed about 1 year ago

Sirisha B. · Reviewed about 1 year ago

Would be interesting to check acces earlier as soon as we start encrypting.

Frederic D. · Reviewed about 1 year ago

Byungsoo J. · Reviewed about 1 year ago

Mohit K. · Reviewed about 1 year ago

Great Lab

Yosua A. · Reviewed about 1 year ago