An enterprise organization uses a multi-project structure in Google Cloud. A Cloud Engineer sets up an organization-level aggregated Log Router sink to export all Cloud Audit logs from all projects to a BigQuery dataset hosted in a dedicated security telemetry project (proj-sec-logs). After configuring the sink filter and destination, the engineer observes that audit logs are not populating the target BigQuery tables. What step must the engineer perform to ensure logs are successfully delivered to BigQuery?
- Grant the unique Writer Identity service account generated by the sink the BigQuery Data Editor role on the destination dataset.Cevap
- BGrant the Organization Administrator primitive role to the default Compute Engine service account at the root organization node.
- CEnable the Cloud Logging API at the Organization resource level instead of individual project settings.
- DRely on organization IAM policy inheritance to automatically grant BigQuery write access to all child project log writers.
Cevap
Grant the unique Writer Identity service account generated by the sink the BigQuery Data Editor role on the destination dataset.
When a Log Router sink routes logs to a destination in another project (such as a BigQuery dataset in a central security project), Google Cloud creates a unique service account called a Writer Identity for that sink. To complete log delivery, that Writer Identity service account must be granted appropriate write permissions (such as BigQuery Data Editor) directly on the target dataset.
Adım Adım Çözüm
Anahtar Kavram
Cross-Project Log Router Sink Ingestion and Writer Identity Authorization
Tahmini Süre:2m 0s