A cloud engineer is standardizing security controls across Google Cloud Storage buckets. The team recently enabled Uniform Bucket-Level Access on a bucket named `app-audit-logs` to comply with organization security policies. An automated deployment script now fails when executing `gcloud storage objects add-acl --object=daily_summary.json --rw-grant=...` to grant read access to a downstream processing account. What is the recommended operational fix to grant access while adhering to the security policy?
- Grant the downstream processing account the Storage Object Viewer role on the bucket, using IAM Conditions to restrict permission to the target object path.Cevap
- BTemporarily disable Uniform Bucket-Level Access on the bucket, execute the object ACL command to grant access, and re-enable Uniform Bucket-Level Access.
- CGrant the downstream processing account the primitive Viewer role at the Google Cloud project level.
- DExecute gcloud storage buckets add-acl to apply a bucket-level ACL entry for the downstream account.
Cevap
Grant the downstream processing account the Storage Object Viewer role on the bucket, using IAM Conditions to restrict permission to the target object path.
When Uniform Bucket-Level Access (UBLA) is enabled, Cloud Storage disables ACLs and manages permissions strictly through Cloud IAM. To grant access to specific objects without violating UBLA or granting excessive permissions, administrators should assign predefined Cloud Storage IAM roles (such as Storage Object Viewer) at the bucket level and apply IAM Conditions to scope access to the required object path.
Adım Adım Çözüm
Anahtar Kavram
Uniform Bucket-Level Access & IAM Scoping