关于“Using Customer-Managed Encryption Keys with Cloud Storage and Cloud KMS”的评价

Luciano A. · 已于 about 7 years前审核

Wilberth E. · 已于 about 7 years前审核

Rémi d. · 已于 about 7 years前审核

krishna y. · 已于 about 7 years前审核

Omar S. · 已于 about 7 years前审核

Crispin v. · 已于 about 7 years前审核

Fred S. · 已于 about 7 years前审核

Andy H. · 已于 about 7 years前审核

Bobby J. · 已于 about 7 years前审核

Christian L. · 已于 about 7 years前审核

Dallas B. · 已于 about 7 years前审核

Masi M. · 已于 about 7 years前审核

Fabian L. · 已于 about 7 years前审核

Sergio M. · 已于 about 7 years前审核

Stephen D. · 已于 about 7 years前审核

Min L. · 已于 about 7 years前审核

Jonathan B. · 已于 about 7 years前审核

Thnere is an error. In the text it says: In order to encrypt data, you need to create a KeyRing and a CryptoKey. KeyRings are useful for grouping keys. Keys can be grouped by environment (like test, staging, and prod) or by some other conceptual grouping. For this lab, your KeyRing will be called test and your CryptoKey will be called labkey. But the keyring is not called test.

John J. · 已于 about 7 years前审核

g

Lohit M. · 已于 about 7 years前审核

Guilherme K. · 已于 about 7 years前审核

Aleksandr K. · 已于 about 7 years前审核

Tatsuo A. · 已于 about 7 years前审核

4

Syrus S. · 已于 about 7 years前审核

Tomás G. · 已于 about 7 years前审核

This time was able to continue. but lab itself is bit obsolete. its possible to identify kms key id on bucket object level. its popup window which tells key id used to encrypt.

Arka A. · 已于 about 7 years前审核