Connect Gateway audit logging

This document describes audit logging for Connect Gateway. Google Cloud services write audit logs that record administrative activities and accesses within your Google Cloud resources. For more information, see Cloud Audit Logs overview.

This page was last generated on 2024-05-23 18:50:50 UTC.

Service name

Connect Gateway audit logs use the service name connectgateway.googleapis.com.

Methods by permission type

Connect Gateway audit logs are enabled by turning on audit logging for gkehub.googleapis.com.

Methods that check DATA_READ, DATA_WRITE, and ADMIN_READ permission types are Data Access audit logs. Methods that check ADMIN_WRITE permission types are Admin Activity audit logs.

Permission type Methods
ADMIN_READ google.cloud.gkeconnect.gateway.v1beta1.GatewayService.GetResource
ADMIN_WRITE google.cloud.gkeconnect.gateway.v1beta1.GatewayService.DeleteResource
google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PatchResource
google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PostResource
google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PutResource

Audit logs per API interface

For information about which permissions are evaluated and how for each method, see the Identity and Access Management documentation for Connect Gateway.

google.cloud.gkeconnect.gateway.v1beta1.GatewayService

Details about audit logs associated with methods belonging to google.cloud.gkeconnect.gateway.v1beta1.GatewayService.

google.cloud.gkeconnect.gateway.v1beta1.GatewayService.DeleteResource

  • Method: google.cloud.gkeconnect.gateway.v1beta1.GatewayService.DeleteResource
  • Audit log Type: Admin Activity
  • Permissions:
    • gkehub.gateway.delete - ADMIN_WRITE
  • Method is a Long Running Operation or Streaming: No.
  • Filter for this method: protoPayload.methodName="google.cloud.gkeconnect.gateway.v1beta1.GatewayService.DeleteResource"

google.cloud.gkeconnect.gateway.v1beta1.GatewayService.GetResource

  • Method: google.cloud.gkeconnect.gateway.v1beta1.GatewayService.GetResource
  • Audit log Type: Data Access
  • Permissions:
    • gkehub.gateway.get - ADMIN_READ
  • Method is a Long Running Operation or Streaming: Streaming RPC
  • Filter for this method: protoPayload.methodName="google.cloud.gkeconnect.gateway.v1beta1.GatewayService.GetResource"

google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PatchResource

  • Method: google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PatchResource
  • Audit log Type: Admin Activity
  • Permissions:
    • gkehub.gateway.patch - ADMIN_WRITE
  • Method is a Long Running Operation or Streaming: No.
  • Filter for this method: protoPayload.methodName="google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PatchResource"

google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PostResource

  • Method: google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PostResource
  • Audit log Type: Admin Activity
  • Permissions:
    • gkehub.gateway.post - ADMIN_WRITE
  • Method is a Long Running Operation or Streaming: No.
  • Filter for this method: protoPayload.methodName="google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PostResource"

google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PutResource

  • Method: google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PutResource
  • Audit log Type: Admin Activity
  • Permissions:
    • gkehub.gateway.put - ADMIN_WRITE
  • Method is a Long Running Operation or Streaming: No.
  • Filter for this method: protoPayload.methodName="google.cloud.gkeconnect.gateway.v1beta1.GatewayService.PutResource"

Kubernetes audit logging

In addition to Cloud Audit Logs, Kubernetes audit logging provides a way for administrators to retain, query, process, and alert on events that occur in registered clusters. Administrators can use the logged information to do forensic analysis and real-time alerting, or for cataloging how a fleet of clusters are being used and by whom.

The Connect Agent talks to the local API server running in the registered cluster, and each cluster will have its own set of Kubernetes audit logs. All actions that users perform from the UI through Connect are logged by that cluster.