Create and Manage Cloud Storage Buckets and Encryption Reviews
202598 reviews
Sebastian B. · Reviewed 6 days ago
two wrong describe json commands. there's no lifecycle and versioning thing but lifecycle_config and versioning_enabled fields. fix that
Vijay Singh K. · Reviewed 6 days ago
Bojan Č. · Reviewed 6 days ago
sherman W. · Reviewed 6 days ago
The name of the bucket must be identical to the project name and not as per instructions in the lab.
ajanta b. · Reviewed 6 days ago
Issue with Lab: Does not recognize the setup2 and setup3 html files as encrypted by consumer. Shows as managed by google.
Edward W. · Reviewed 6 days ago
Tushar K. · Reviewed 6 days ago
Problems with task 3 I have done correctly the task to upload files with a costumer-supplied encryption key, but the lab isn't recognizing it. I have tried this lab for at least 3 times already, and it still not working
Tiago S. · Reviewed 6 days ago
there is some problem with this lab or lab instructions. either the updated lab is not in sync with instruction in tutorial or something wrong. same problem i have been facing for three times. the steps or procedure after task 2 is not passing according to the instruction please look into it
Devansh B. · Reviewed 6 days ago
Francisco F. · Reviewed 6 days ago
Rabah G. · Reviewed 6 days ago
HEMANTH S S. · Reviewed 6 days ago
HEMANTH S S. · Reviewed 6 days ago
JAMES M S. · Reviewed 6 days ago
Part about encryption is not working correctly. Tried different ways of changing that and even was able to achieve customer-supplied encryption instead of google-managed, but couldn't successfully pass the checkpoint.
Krzysztof K. · Reviewed 6 days ago
Issue Description: The "Check my Progress" button for Task 3 (Customer-supplied encryption keys) is broken and does not award the 20 points, even when files are successfully customer-encrypted. Technical Root Cause: The lab instructions provide a mix of two different CLI tools for the encryption sequence: gsutil kms encryption -d gs://$BUCKET_NAME_1 gcloud storage cp setup2.html gs://$BUCKET_NAME_1/ Because gcloud storage completely ignores the ~/.boto configuration file where the encryption key is stored, these commands upload the files using standard Google-managed encryption instead of Customer-supplied encryption (CSEK). When I manually patched this by forcing the encryption via explicit flags, the files became properly customer-encrypted in the console. However, the automated "Check my Progress" script still failed to recognize it and denied the 20 points, likely because it strictly looks for a command history or metadata state generated only by the broken default commands. Suggested Fix: Update the validation script and the lab instructions to use one consistent CLI tool (either entirely gsutil or entirely gcloud storage) so that the progress check works and students receive their points.
Marina B. · Reviewed 6 days ago
not working Customer-supplied encryption keys.
Andrii H. · Reviewed 6 days ago
No task 3 was completly broken
Salvador Basso C. · Reviewed 6 days ago
The lab checker for Task 3 (CSEK) is completely broken. I successfully uploaded setup2.html and setup3.html with AES-256 customer-supplied encryption keys, verified with gsutil stat showing Encryption algorithm: AES256 on both files, yet the checker kept returning 0 points. I spent my entire lab session on this single task due to two undocumented issues: (1) the instructions tell you to run gsutil kms encryption -d which silently breaks CSEK uploads, and (2) newly created buckets have an org-level policy restricting CSEK that is never mentioned anywhere. The lab needs a full rewrite. Extremely frustrating experience.
Firmin T. · Reviewed 6 days ago
Aunque completado el paso 3, no me lo reconoce como hecho
David S. · Reviewed 6 days ago
Poor lab - commands do not work properly
Nizar M. · Reviewed 6 days ago
jennifer m. · Reviewed 6 days ago
cool
Varsha Sagar K. · Reviewed 6 days ago
Absolute garbage, every time. A waste of my life. Every time.
Dustin J. · Reviewed 6 days ago
Praveen S. · Reviewed 6 days ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.