Opinie (Create and Manage Cloud Storage Buckets and Encryption)

3 чек прогрес не працює хоть я робив все правильно

NAZAR B. · Sprawdzono 4 dni temu

ok

priyanka g. · Sprawdzono 4 dni temu

Sai Aditya Praveen V. · Sprawdzono 4 dni temu

ok

priyanka g. · Sprawdzono 4 dni temu

CSEK keys didn't add or rotate with instructions

Ryan J. · Sprawdzono 4 dni temu

the check on the 3rd CSEK keep failing for no reason or I'm unable to uploaded the setup2 and setup3 since they does not match with the bucket policy of allowing CSEK.

Son T. · Sprawdzono 4 dni temu

Elmir G. · Sprawdzono 4 dni temu

Hugo Fabiano L. · Sprawdzono 4 dni temu

Taylor G. · Sprawdzono 4 dni temu

Adam F. · Sprawdzono 4 dni temu

Jose Manuel S. · Sprawdzono 4 dni temu

Ike O. · Sprawdzono 4 dni temu

Sudhir S. · Sprawdzono 4 dni temu

had to toggle the CSEK config in the bucket in console to allow it at this point: Upload the remaining setup files (encrypted) and verify in the Cloud Console. there was no instruction for this.

Patrick Gerard B. · Sprawdzono 4 dni temu

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.

Gustavo D. · Sprawdzono 4 dni temu

건현 박. · Sprawdzono 4 dni temu

Yahya Ö. · Sprawdzono 4 dni temu

have to restart the lab because the command to copy the files in after setting up bucket encryption isn't working. followed the steps up to that point, and tried to debug the issue, but just didn't work

Patrick Gerard B. · Sprawdzono 4 dni temu

CHRISTIAN FRANCESCO D. · Sprawdzono 4 dni temu

Shubhranshu S. · Sprawdzono 4 dni temu

Julian Alberto V. · Sprawdzono 4 dni temu

Naresh S. · Sprawdzono 4 dni temu

encryption is not working

Mohammed K. · Sprawdzono 4 dni temu

Preethika G. · Sprawdzono 4 dni temu

Shubhranshu S. · Sprawdzono 4 dni temu