Using Customer-Supplied Encryption Keys with Cloud Storage Reviews

Matt Y. · Reviewed about 7 years ago

Cristian P. · Reviewed about 7 years ago

Joel F. · Reviewed about 7 years ago

ok

Beaumadier B. · Reviewed about 7 years ago

Mos S. · Reviewed about 7 years ago

Dariusz T. · Reviewed about 7 years ago

Jean-Remi P. · Reviewed about 7 years ago

Ashley C. · Reviewed about 7 years ago

Guillaume B. · Reviewed about 7 years ago

Aleksandr S. · Reviewed about 7 years ago

Harold M. · Reviewed about 7 years ago

Gaurav S. · Reviewed about 7 years ago

Wilson C. · Reviewed about 7 years ago

Igor G. · Reviewed about 7 years ago

google2825098_student@cseklab-vm:~$ gsutil cp setup2.html gs://$BUCKET_NAME CommandException: "cp" command does not support provider-only URLs.

Murugesu C. · Reviewed about 7 years ago

bobby c. · Reviewed about 7 years ago

Sam M. · Reviewed about 7 years ago

Jingfeng L. · Reviewed about 7 years ago

Igor K. · Reviewed about 7 years ago

Allen C. · Reviewed about 7 years ago

Jonathan C. · Reviewed about 7 years ago

consider using $DEVSHELL_PROJECT_ID instead of getting the user to type the project name. Consider using SED to add the encryption key by finding and replacing text in the .boto file. crtl W does not work in cloud shell which makes finding the text to replace difficult. Consider writing the encryption key out to file to make copy and pasting easier. See Configuring, using, and auditing VM service accounts and scopes and Encrypting Disks with Customer-Supplied Encryption Keys for ways that this has been made easier.

Paul B. · Reviewed about 7 years ago

5 stars = Very satisfied

Cristhian A. · Reviewed about 7 years ago

behnaz f. · Reviewed about 7 years ago

Murali K. · Reviewed about 7 years ago