Create and Manage Cloud Storage Buckets and Encryption Reviews
202640 reviews
Customer-supplied encryption keys (CSEK) - not captured progress - tried two times
Shridhara A. · Reviewed 22 days ago
Task 3 doesn't work. I've tried different approaches with gcloud and gsutil
Aleksandr K. · Reviewed 22 days ago
Can't finish this lab error in "customer-supplied encryption keys" I managed to upload with "gcloud storage cp setup2.html gs://$BUCKET_NAME_1/ --encryption-key=". However, the validation still failed
David M. · Reviewed 22 days ago
by org policy I cannot add csek so I got stuck mid lab and could not finish
Guido F. · Reviewed 22 days ago
Shridhara A. · Reviewed 22 days ago
the customer encryption is broken. Tried many times and it didn't go through.
Grzegorz M. · Reviewed 22 days ago
Teo S. · Reviewed 22 days ago
La tercera parte del laboratorio referente a la encriptacion nunca cargo
Angelo Antonio C. · Reviewed 22 days ago
Varsha Sagar K. · Reviewed 22 days ago
Ioana D. · Reviewed 22 days ago
Karim G. · Reviewed 22 days ago
Ioana D. · Reviewed 22 days ago
smaranika P. · Reviewed 22 days ago
customer supplied encryption key didnt work
REENISH K. · Reviewed 22 days ago
Ioana D. · Reviewed 22 days ago
customer supplied encryption key didnt work
REENISH K. · Reviewed 22 days ago
Ahmad A. · Reviewed 22 days ago
Євген Б. · Reviewed 22 days ago
SEDHURAMAN A. · Reviewed 22 days ago
Can't finish this lab error in "customer-supplied encryption keys".This lab contains outdated information. 1.352 This PreconditionException: 412 error is a known issue that has recently started occurring in this Qwiklabs lab. Google Cloud has released a security feature called Encryption Enforcement Rules which, in some new Qwiklabs environments, is configured by default to block customer-managed keys (CSEK), causing the gsutil cp command to fail. Since the lab script is outdated and doesn't mention this new step, you need to manually allow the use of customer-supplied keys (CSEK) in the console interface before running the commands. Follow these steps to fix it: 1. Adjust the encryption policy in the GCP Console In the Google Cloud Console, access the navigation menu and go to Cloud Storage > Buckets. Click on your bucket name ([BUCKET_NAME_1]). Click on the Configuration tab at the top. Scroll down to the Protection section and click Edit encryption. In the Encryption enforcement rules section, locate the option for Customer-supplied keys (CSEK). Change its status to Allowed or Not Restricted. Click Save. Note: It may take up to 1 or 2 minutes for the change to propagate.
David M. · Reviewed 22 days ago
Rushikesh G. · Reviewed 22 days ago
Raimonds B. · Reviewed 22 days ago
KAI W. · Reviewed 22 days ago
SEDHURAMAN A. · Reviewed 22 days ago
gcloud is not working with boto file and task 3 is never completed even after using gsutil
Sasin N. · Reviewed 22 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.