This document shows you how to grant Identity and Access Management (IAM) roles and permissions to support routing events from Google Cloud and other sources to Cloud Run services using Eventarc:
Grant project-wide permissions to the principal invoking the Eventarc APIs (for example, the Eventarc trigger creator):
- The Eventarc Admin role allows you full control over all Eventarc resources, including specifying a service account for the trigger when you create it.
- The Service Account User role allows a principal to impersonate and use a service account. The service account is associated with an Eventarc trigger and represents the identity of the trigger.
Grant Eventarc trigger permissions to the trigger service account: The Eventarc Event Receiver role allows your Eventarc trigger to receive events from event providers. You don't need to grant the role if you are routing direct events from Cloud Pub/Sub.
Grant Cloud Run service permissions to the trigger service account: The Cloud Run Invoker role allows your Eventarc trigger to call the target Cloud Run service. This applies if you are routing events to an authenticated Cloud Run service.
- If you are creating a trigger for direct events from Cloud Storage, grant the Pub/Sub Publisher role.
- If you enabled the Cloud Pub/Sub service agent on or before April 8, 2021, grant the Service Account Token Creator role.
Grant project-wide permissions
If you are the project creator, you are granted the
basic Owner role (
default, this role includes the permissions necessary for full access to most
Google Cloud resources. Otherwise, required roles must be granted by an
administrator on the appropriate resource to the appropriate principal (also
known as a member).
For example, a principal can be a Google Account (for end users) or a service account (for applications and compute workloads). Each principal has its own identifier, which is typically an email address.
The Eventarc Admin role (
roles/eventarc.admin) allows you full control over all Eventarc resources.
Grant the role on the project:
gcloud projects add-iam-policy-binding PROJECT_ID \ --member=PRINCIPAL \ --role=roles/eventarc.admin
Replace the following:
PROJECT_ID: your Google Cloud project ID.
PRINCIPAL: an identifier for the trigger creator which usually has the following form:
PRINCIPAL_TYPE:ID. For example,
user:email@example.com. For a full list of the possible
PRINCIPAL_TYPEvalues, see the Policy Binding reference.
The Service Account User role (
roles/iam.serviceAccountUser) allows a principal to run operations as a service account.
For example, you need this role so that you can associate a user-managed service account with an Eventarc trigger. You also need it so that you can act as the runtime service account when deploying a Cloud Run service. For more information, see Roles for service account authentication.
You can either grant the role on the project to allow the principal to impersonate multiple service accounts or grant the role on the service account to allow the principal to impersonate only a specific service account.
Grant the role on the project:
gcloud projects add-iam-policy-binding PROJECT_ID \ --member=PRINCIPAL \ --role=roles/iam.serviceAccountUser
Or, grant the role on the service account:
gcloud iam service-accounts add-iam-policy-binding \ projects/SERVICE_ACCOUNT_PROJECT_ID/serviceAccounts/SERVICE_ACCOUNT_NAME@SERVICE_ACCOUNT_PROJECT_ID.iam.gserviceaccount.com \ --member=PRINCIPAL \ --role=roles/iam.serviceAccountUser
Replace the following:
SERVICE_ACCOUNT_PROJECT_ID: the Google Cloud project ID that contains the service account.
SERVICE_ACCOUNT_NAME: the name of the service account.
Grant Eventarc trigger permissions
Every Eventarc trigger is associated with an IAM service account at the time the trigger is created. You can specify a user-managed service account that the trigger uses as its default identity. If you don't specify a service account during the trigger's creation, the trigger uses the Compute Engine default service account for its identity.
We recommend that you create your own user-managed service account to give you greater control and flexibility when managing your trigger.
Create a service account and note its name:
gcloud iam service-accounts create SERVICE_ACCOUNT_NAME \ --description="DESCRIPTION" \ --display-name="DISPLAY_NAME"
Replace the following:
SERVICE_ACCOUNT_NAME: the name of the service account. This name appears in the email address that identifies the service account.
DESCRIPTION: an optional description of the service account
DISPLAY_NAME: a service account name to display in the Google Cloud console
Grant the Eventarc Event Receiver role (
roles/eventarc.eventReceiver) on the project to the service account associated with your Eventarc trigger so that the trigger can receive events from event providers.
Note that you don't need to grant the Eventarc Event Receiver role if you are routing direct events from Cloud Pub/Sub.
gcloud projects add-iam-policy-binding PROJECT_ID \ --member=serviceAccount:SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com \ --role=roles/eventarc.eventReceiver
SERVICE_ACCOUNT_NAMEwith the name of your service account that you noted in the previous step.
Grant Cloud Run service permissions
All Cloud Run services are deployed privately by default, which means that they can't be accessed without providing authentication credentials in the request. For projects with domain restricted sharing organization policies, use an authenticated Cloud Run target service rather than one that allows public (unauthenticated) access.
By default, Cloud Run services are only callable by Project Owners, Project Editors, Cloud Run Admins, and Cloud Run Invokers.
If you are routing events to an authenticated Cloud Run target service, grant the Cloud Run Invoker role (
run.invoker) on the Cloud Run service to the user-managed service account associated with your Eventarc trigger:
gcloud run services add-iam-policy-binding SERVICE_NAME \ --member=serviceAccount:SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com \ --role=roles/run.invoker
SERVICE_NAMEwith the name of the Cloud Run service.
Optionally, you can grant the role on all Cloud Run services and jobs in a Google Cloud project. For more information, see Control access on all services and jobs in a project.
Note that if you create a trigger for an authenticated Cloud Run service without granting the Cloud Run Invoker role, the trigger is created successfully and is active. However, the trigger will not work as expected and a message similar to the following appears in the logs:
The request was not authenticated. Either allow unauthenticated
invocations or set the proper Authorization header.
Grant permissions to Google service agents
Some Google Cloud services have Google-managed service accounts that allow the services to access your resources. These service accounts are known as service agents. If an API requires a service agent, then Google creates the service agent after you activate and use the API.
If you are creating a trigger for direct events from Cloud Storage, to support publishing messages to a topic, grant the Pub/Sub Publisher role (
roles/pubsub.publisher) on the project to the Cloud Storage service agent:
gcloud projects add-iam-policy-binding PROJECT_ID \ --member=serviceAccount:service-PROJECT_NUMBER@gs-project-accounts.iam.gserviceaccount.com \ --role=roles/pubsub.publisher
PROJECT_NUMBERwith your Google Cloud project number. You can find your project number on the Dashboard page of the Google Cloud console or by running the following command:
gcloud projects describe PROJECT_ID --format='value(projectNumber)'
If you enabled the Cloud Pub/Sub service agent on or before April 8, 2021, to support authenticated Pub/Sub push requests, grant the Service Account Token Creator role (
roles/iam.serviceAccountTokenCreator) on the project to the Pub/Sub service agent. Otherwise, this role is granted by default:
gcloud projects add-iam-policy-binding PROJECT_ID \ --member=serviceAccount:service-PROJECT_NUMBER@gcp-sa-pubsub.iam.gserviceaccount.com \ --role=roles/iam.serviceAccountTokenCreator
Learn about access control options in Eventarc.
Learn about best practices for using service accounts.