Using Customer-Supplied Encryption Keys with Cloud Storage Reviews

Gianfranco P. · Reviewed больше 1 года ago

great labs

Boy A. · Reviewed больше 1 года ago

ANUJ A. · Reviewed больше 1 года ago

Scott K. · Reviewed больше 1 года ago

Pablo S. · Reviewed больше 1 года ago

Jiye N. · Reviewed больше 1 года ago

Jieqing O. · Reviewed больше 1 года ago

Himanshu S. · Reviewed больше 1 года ago

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

manish s. · Reviewed больше 1 года ago

Stevie S. · Reviewed больше 1 года ago

Nadia M. · Reviewed больше 1 года ago

Jose R. · Reviewed больше 1 года ago

Johan C. · Reviewed больше 1 года ago

승민 이. · Reviewed больше 1 года ago

세은 배. · Reviewed больше 1 года ago

Sara L. · Reviewed больше 1 года ago

Sara L. · Reviewed больше 1 года ago

Paulo L. · Reviewed больше 1 года ago

Shan M. · Reviewed больше 1 года ago

Sunil W. · Reviewed больше 1 года ago

fidel a. · Reviewed больше 1 года ago

Marius A. · Reviewed больше 1 года 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 больше 1 года ago

Musheer A. · Reviewed больше 1 года ago

Sirisha B. · Reviewed больше 1 года ago