Opinie (Create and Manage Cloud Storage Buckets and Encryption)

fix the instructions!

Pocholo Ryan D. · Sprawdzono 1 dzień temu

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

John Dominic U. · Sprawdzono 1 dzień temu

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. · Sprawdzono 1 dzień temu

Vivek Reddy K. · Sprawdzono 1 dzień temu

tried many times enough task is completed its not getting updated

Sowndar T. · Sprawdzono 1 dzień temu

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. · Sprawdzono 1 dzień temu

Task 3 does not work kindly fix the test !

Abir E. · Sprawdzono 1 dzień temu

Josue G. · Sprawdzono 1 dzień temu

Keep retrying. Check still fails.

Hugo Enrique M. · Sprawdzono 1 dzień temu

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

Sergio C. · Sprawdzono 1 dzień temu

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

Richard R. · Sprawdzono 1 dzień temu

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. · Sprawdzono 1 dzień temu

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

Hugo Enrique M. · Sprawdzono 1 dzień temu

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

ANDREW R. · Sprawdzono 1 dzień temu

Cristian M. · Sprawdzono 1 dzień temu

Oleksandr N. · Sprawdzono 1 dzień temu

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

Sergio C. · Sprawdzono 1 dzień temu

Cristian M. · Sprawdzono 1 dzień temu

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

Mateusz R. · Sprawdzono 1 dzień temu

JIGYASA T. · Sprawdzono 1 dzień temu

Raju B. · Sprawdzono 1 dzień temu

Agata F. · Sprawdzono 1 dzień temu

Lab seems to have bugs

Steve C. · Sprawdzono 1 dzień temu

Patrick D. · Sprawdzono 1 dzień temu

Gabriel O. · Sprawdzono 1 dzień temu