Create and Manage Cloud Storage Buckets and Encryption Reviews
201291 reviews
Luciano d. · Reviewed 1 day ago
use lessnnn
JIGYASA T. · Reviewed 1 day ago
Excelent Excersice
Octavio S. · Reviewed 1 day ago
gsutil kms encryption -d gs://$BUCKET_NAME_1 ? -d flag stands for disassociate ?!
To P. · Reviewed 1 day ago
El check de CSEK esta malo. subi los archivos encriptados con CSEK, aparece que estan encriptados de esa manera para aun asi no pasa el check.
Jorge C. · Reviewed 1 day ago
Lucas B. · Reviewed 1 day ago
use less
JIGYASA T. · Reviewed 1 day ago
JIGYASA T. · Reviewed 1 day ago
Inés Ariadna V. · Reviewed 1 day ago
The CSEK portion was not working and I spent an hour going back to redoing it three times including using Gemini. I could not resolve the issue.
Tina K. · Reviewed 1 day ago
Luis G. · Reviewed 1 day ago
Davi J. · Reviewed 1 day ago
once it came to task 4 no matter what i did correctly and tried multiple times with same result
Austin R. · Reviewed 1 day ago
Lucas B. · Reviewed 1 day ago
very bad experience, I followed all the steps, but not able to finish the lab, it said that I was not able to copy files to the bucket using customer supplied key, so obviously this command doesn't work gsutil kms encryption -d gs://$BUCKET_NAME_1 gcloud storage cp setup2.html gs://$BUCKET_NAME_1/ gcloud storage cp setup3.html gs://$BUCKET_NAME_1/ still I used another one that showed that I objects are copied using customer supplied key, but lab didn't consider it as success, very bad experience
Petr M. · Reviewed 1 day ago
Alexander H. · Reviewed 1 day ago
lab com bug
Giuliano D. · Reviewed 1 day ago
yaseen a. · Reviewed 1 day ago
Fix the lab please
Kacper S. · Reviewed 1 day ago
Víctor C. · Reviewed 1 day ago
Karthik K. · Reviewed 1 day ago
lab com bug
Giuliano D. · Reviewed 1 day ago
fix the instructions!
Pocholo Ryan D. · Reviewed 1 day ago
Cannot continue since the Encryption is still being set to 'Google-managed' instead of 'Customer-supplied encryption keys'.
John Dominic U. · Reviewed 1 day ago
I believe this lab has a bug causing users to not pass step 3. If not, I feel as if more guidance is needed outside of the given instructions for learners. One primary issue I believe is coming in the Bucket creation steps. The instructions do not direct any changes to the buckets encryption settings leaving keys defaulted to Google Managed keys. Even with the creation and editing of the .boto file, when the copied files setup2 and setup3 are uploaded to the bucket, they are done so as Google Managed encryption keys. I also tried to change the settings both on initial runs as well as after failure. Once the settings are changed, I am about to upload the files successfully as Customer-Supplied Encryption Keys however the lab does not read this and I am still unable to pass that checkpoint.
Kristopher B. · Reviewed 1 day ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.