Opinie (Using Customer-Managed Encryption Keys with Cloud Storage and Cloud KMS)

Dheeraj S. · Sprawdzono ponad 6 lat temu

Can't upload file into bucket

Claudio P. · Sprawdzono ponad 6 lat temu

Martin M. · Sprawdzono ponad 6 lat temu

Pedro O. · Sprawdzono ponad 6 lat temu

Anurag T. · Sprawdzono ponad 6 lat temu

global keyrings are not compatible with US buckets. Required lots of effort to have score completed. Needed to make second keyring

Emily C. · Sprawdzono ponad 6 lat temu

Need to change GCS location. Because when you use global key in region US GCS, gsutil returns: BadRequestException: 400 Cloud KMS region 'global' not available for use with GCS region 'US'.

Heryudi G. · Sprawdzono ponad 6 lat temu

Error with this Lab: student_00_5d474bc34f1c@cloudshell:~ (qwiklabs-gcp-00-59483ae27010)$ gsutil cp file2.txt gs://$DEVSHELL_PROJECT_ID-kms Copying file://file2.txt [Content-Type=text/plain]... BadRequestException: 400 Cloud KMS region 'global' not available for use with GCS region 'US'. a lot of issues .. after many retrials, i am no more able to create the bucket (the first command of the lab !!!) message sent to Support !!

Michel K. · Sprawdzono ponad 6 lat temu

BadRequestException: 400 Cloud KMS region 'global' not available for use with GCS region 'US'.

Jacek K. · Sprawdzono ponad 6 lat temu

The lab is broken for US users: BadRequestException: 400 Cloud KMS region 'global' not available for use with GCS region 'US'. I was able to finish by updating the commands to this: gsutil kms encryption -k \ projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings\ /$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME \ gs://$DEVSHELL_PROJECT_ID-kms gcloud kms keys create $CRYPTOKEY_1_NAME --location us \ --keyring $KEYRING_NAME --purpose encryption gcloud kms keys create $CRYPTOKEY_2_NAME --location us \ --keyring $KEYRING_NAME --purpose encryption gsutil kms authorize -p $DEVSHELL_PROJECT_ID -k \ projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings\ /$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME gsutil kms authorize -p $DEVSHELL_PROJECT_ID -k \ projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings\ /$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_2_NAME gsutil kms encryption -k \ projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings\ /$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_1_NAME \ gs://$DEVSHELL_PROJECT_ID-kms gsutil -o \ "GSUtil:encryption_key=projects/$DEVSHELL_PROJECT_ID/locations/us/keyRings\ /$KEYRING_NAME/cryptoKeys/$CRYPTOKEY_2_NAME" \ cp file3.txt gs://$DEVSHELL_PROJECT_ID-kms

Rafael C. · Sprawdzono ponad 6 lat temu

Dheeraj S. · Sprawdzono ponad 6 lat temu

Pakorn N. · Sprawdzono ponad 6 lat temu

Cristian M. · Sprawdzono ponad 6 lat temu

Ivan J. · Sprawdzono ponad 6 lat temu

Le D. · Sprawdzono ponad 6 lat temu

Lab has a bug. "Cloud KMS region 'global' not available for use with GCP region 'US'

Nicolas V. · Sprawdzono ponad 6 lat temu

BadRequestException: 400 Cloud KMS region 'global' not available for use with GCS region 'US'.

Jacek K. · Sprawdzono ponad 6 lat temu

Anton H. · Sprawdzono ponad 6 lat temu

BadRequestException: 400 Cloud KMS region 'global' not available for use with GCS region 'US'.

Jacek K. · Sprawdzono ponad 6 lat temu

there is the problem with the global for keyring, need to do the lab again

Konstantinos B. · Sprawdzono ponad 6 lat temu

again....frustrating...another lab not functioning correctly....

David S. · Sprawdzono ponad 6 lat temu

Bugged

Ignacio C. · Sprawdzono ponad 6 lat temu

keys in global region resulting in error. Lab doesn't acknowledge steps when completed in US region.

Anita S. · Sprawdzono ponad 6 lat temu

I was unable to complete the lab since I couldn't copy file2.txt to my bucket. I got the same exception when trying to use a EU-bucket I got this exception: BadRequestException: 400 Cloud KMS region 'global' not available for use with GCS region 'US'.

Martin Bahn E. · Sprawdzono ponad 6 lat temu

Andrew N. · Sprawdzono ponad 6 lat temu