Відгуки: Create and Manage Cloud Storage Buckets and Encryption

fix the instructions!

Pocholo Ryan D. · Відгук надано 1 день тому

Cannot continue since the Encryption is still being set to 'Google-managed' instead of 'Customer-supplied encryption keys'.

John Dominic U. · Відгук надано 1 день тому

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. · Відгук надано 1 день тому

Vivek Reddy K. · Відгук надано 1 день тому

tried many times enough task is completed its not getting updated

Sowndar T. · Відгук надано 1 день тому

The check for Task 3 doesn't work. Steps from Task 3 and Task 4 have issues I guess. There's an issue with Syntax with Task 4, Step 3. Uncomment decryption\_key1 by removing the # character, and copy the current key from the encryption\_key line to the decryption\_key1 line. Neither 'encryption\_key' nor 'decryption\_key' exist in the .boto file in the explanation. Can I get an update on this?

Hugo Enrique M. · Відгук надано 1 день тому

Task 3 does not work kindly fix the test !

Abir E. · Відгук надано 1 день тому

Josue G. · Відгук надано 1 день тому

Keep retrying. Check still fails.

Hugo Enrique M. · Відгук надано 1 день тому

encryption does not worked bucket details, key of lifecycle and versioning changed to lifecycle_config and versioning_enabled

Sergio C. · Відгук надано 1 день тому

uno de los pasos para las claves proporcionadas por cliente no sirve bien.

Richard R. · Відгук надано 1 день тому

The lab was updated but it is not correct. New command in step 3, fails: gsutil kms encryption -d gs://$BUCKET_NAME_1 Google recommends using Gcloud storage CLI (https://docs.cloud.google.com/storage/docs/discover-object-storage-gcloud) instead of gsutil. Please refer to migration guide (https://docs.cloud.google.com/storage/docs/gsutil-transition-to-gcloud) for assistance. You are attempting to perform an operation that requires a project id, with none configured. Please re-run gsutil config and make sure to follow the instructions for finding and entering your default project id.

David M. · Відгук надано 1 день тому

I followed all steps but the progress check is failing after .boto

Hugo Enrique M. · Відгук надано 1 день тому

gcloud vs gsutil commands caused csek not to be recognized even when actually in use

ANDREW R. · Відгук надано 1 день тому

Cristian M. · Відгук надано 1 день тому

Oleksandr N. · Відгук надано 1 день тому

encryption does not worked bucket details, key of lifecycle and versioning changed to lifecycle_config and versioning_enabled

Sergio C. · Відгук надано 1 день тому

Cristian M. · Відгук надано 1 день тому

encrypted key part in task is not working good-in not working );

Mateusz R. · Відгук надано 1 день тому

JIGYASA T. · Відгук надано 1 день тому

Raju B. · Відгук надано 1 день тому

Agata F. · Відгук надано 1 день тому

Lab seems to have bugs

Steve C. · Відгук надано 1 день тому

Patrick D. · Відгук надано 1 день тому

Gabriel O. · Відгук надано 1 день тому