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.


> [!NOTE]
> **Note:** If you want to attach a service account in one project to an Eventarc trigger in another project, you must first complete the steps outlined in [Support a cross-project service account](https://docs.cloud.google.com/eventarc/docs/use-cross-project-service-account.md.txt).

<br />

1. [Grant project-wide permissions to the principal invoking the Eventarc APIs](https://docs.cloud.google.com/eventarc/docs/roles-permissions.md.txt#project-perms)
   (for example, the Eventarc trigger creator):

   1. The **Eventarc Admin** role allows you full control over all Eventarc resources, including specifying a service account for the trigger when you create it.
   2. The **Service Account User** role allows a principal to impersonate and use a service account. It allows a principal to attach a user-managed service account to an Eventarc trigger and act as the runtime service account when deploying a Cloud Run service.
2. [Grant Eventarc trigger permissions to the trigger service account](https://docs.cloud.google.com/eventarc/docs/roles-permissions.md.txt#trigger-perms):
   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.

3. [Grant Cloud Run service permissions to the trigger service account](https://docs.cloud.google.com/eventarc/docs/roles-permissions.md.txt#invoker-role):
   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.

4. [Grant permissions to Google service agents](https://docs.cloud.google.com/eventarc/docs/roles-permissions.md.txt#agent-perms):

   1. The **Eventarc Service Agent** role allows the Eventarc
      service agent to manage underlying transport resources and validate event
      sources. This role is granted by default when you create an
      Eventarc resource for the first time, but you must restore it
      if it is removed.

   2. If you are creating a trigger for direct events from Cloud Storage, grant
      the **Pub/Sub Publisher** role to the Cloud Storage service agent.

   3. If you enabled the Cloud Pub/Sub service agent on or before
      April 8, 2021, grant the **Service Account Token Creator** role to the
      Pub/Sub service agent.

For more information about granting IAM roles, see
[Manage access](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt). You might also be
able to get the required permissions through
[custom roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles.md.txt) or other
[predefined roles](https://docs.cloud.google.com/iam/docs/understanding-roles).

## Grant project-wide permissions

If you are the project creator, you are granted the
[basic Owner role](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#basic) (`roles/owner`). By
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.

1. The [Eventarc Admin role](https://docs.cloud.google.com/iam/docs/roles-permissions/eventarc.md.txt#eventarc.admin)
   (`roles/eventarc.admin`) allows you full control over all Eventarc
   resources.

   Grant the role on the project:

   ```bash
   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:my-user@example.com`. For a full list of the possible `PRINCIPAL_TYPE` values, see the [Policy Binding reference](https://docs.cloud.google.com/iam/docs/reference/rest/v1/Policy.md.txt#Binding).
2. The [Service Account User role](https://docs.cloud.google.com/iam/docs/roles-permissions/iam.md.txt#iam.serviceAccountUser)
   (`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](https://docs.cloud.google.com/run/docs/securing/service-identity.md.txt)
   when deploying a Cloud Run service (for additional roles
   required to deploy a service, see
   [Required roles for deploying Cloud Run services](https://docs.cloud.google.com/run/docs/deploying.md.txt#required_roles)).
   For more information, see
   [Roles for service account authentication](https://docs.cloud.google.com/iam/docs/service-account-permissions.md.txt).

   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:

   ```bash
   gcloud projects add-iam-policy-binding PROJECT_ID \
       --member=PRINCIPAL \
       --role=roles/iam.serviceAccountUser
   ```

   Or, grant the role on the service account:

   ```bash
   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](https://docs.cloud.google.com/iam/docs/service-account-types.md.txt#default)
for its identity.

> [!CAUTION]
> **Caution:** For production environments, we strongly recommend creating a new service account and granting it one or more IAM roles that contain the [minimum permissions required](https://docs.cloud.google.com/iam/docs/best-practices-service-accounts.md.txt#limit-service-account-privileges). You shouldn't use the default service account since it is automatically granted the highly privileged [basic Editor role](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#basic).

We recommend that you
[create your own user-managed service account](https://docs.cloud.google.com/iam/docs/creating-managing-service-accounts#creating)
to give you greater control and flexibility when managing your trigger.

1. Create a service account and note its name:

   ```bash
   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.
2. Grant the
   [Eventarc Event Receiver role](https://docs.cloud.google.com/iam/docs/roles-permissions/eventarc.md.txt#eventarc.eventReceiver)
   (`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](https://docs.cloud.google.com/eventarc/standard/docs/run/route-trigger-cloud-pubsub.md.txt).

   ```bash
   gcloud projects add-iam-policy-binding PROJECT_ID \
       --member=serviceAccount:SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com \
       --role=roles/eventarc.eventReceiver
   ```

   Replace `SERVICE_ACCOUNT_NAME` with 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](https://docs.cloud.google.com/resource-manager/docs/organization-policy/restricting-domains),
use an authenticated Cloud Run target service rather than one
that allows [public (unauthenticated) access](https://docs.cloud.google.com/run/docs/authenticating/public.md.txt).

By default, Cloud Run services are only callable by Project
Owners, Project Editors, Cloud Run Admins, and
Cloud Run Invokers.

1. **If you are routing events to an authenticated Cloud Run
   target service** , grant the
   [Cloud Run Invoker role](https://docs.cloud.google.com/iam/docs/roles-permissions/run.md.txt#run.invoker)
   (`roles/run.invoker`) on the Cloud Run service to the
   user-managed service account associated with your Eventarc
   trigger:

   ```bash
   gcloud run services add-iam-policy-binding SERVICE_NAME \
       --region=REGION \
       --member=serviceAccount:SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com \
       --role=roles/run.invoker
   ```

   Replace the following:
   - `SERVICE_NAME`: the name of the Cloud Run service.
   - `REGION`: the region where your Cloud Run service is deployed.
2. 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](https://docs.cloud.google.com/run/docs/securing/managing-access.md.txt#control-access-on-all-services).

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 won't 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
[*service agents*](https://docs.cloud.google.com/iam/docs/service-agents.md.txt) that allow the
services to access your resources. If an API requires a service agent, then
Google creates the service agent after you activate and use the API.

1. **If the [Eventarc Service Agent role](https://docs.cloud.google.com/iam/docs/roles-permissions/eventarc.md.txt#eventarc.serviceAgent)
   (`roles/eventarc.serviceAgent`) was removed from the Eventarc
   service agent**, grant the role on the project so that Eventarc
   can manage underlying transport resources and validate event sources. Otherwise,
   this role is granted by default when you create an Eventarc
   resource for the first time:

   ```bash
   gcloud projects add-iam-policy-binding PROJECT_ID \
       --member=serviceAccount:service-PROJECT_NUMBER@gcp-sa-eventarc.iam.gserviceaccount.com \
       --role=roles/eventarc.serviceAgent
   ```

   Replace `PROJECT_NUMBER` with your Google Cloud
   project number. You can find your project number on the
   [Welcome](https://console.cloud.google.com/welcome)
   page of the Google Cloud console or by running the following command:

   ```bash
   gcloud projects describe PROJECT_ID --format='value(projectNumber)'
   ```
2. **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](https://docs.cloud.google.com/iam/docs/roles-permissions/pubsub.md.txt#pubsub.publisher)
   (`roles/pubsub.publisher`) on the project to the Cloud Storage service
   agent:

   ```bash
   gcloud projects add-iam-policy-binding PROJECT_ID \
       --member=serviceAccount:service-PROJECT_NUMBER@gs-project-accounts.iam.gserviceaccount.com \
       --role=roles/pubsub.publisher
   ```
3. **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](https://docs.cloud.google.com/iam/docs/roles-permissions/iam.md.txt#iam.serviceAccountTokenCreator)
   (`roles/iam.serviceAccountTokenCreator`) on the project to the
   Pub/Sub service agent. Otherwise, this role is granted by
   default:

   ```bash
   gcloud projects add-iam-policy-binding PROJECT_ID \
       --member=serviceAccount:service-PROJECT_NUMBER@gcp-sa-pubsub.iam.gserviceaccount.com \
       --role=roles/iam.serviceAccountTokenCreator
   ```

## What's next

- Learn about
  [access control options in Eventarc](https://docs.cloud.google.com/eventarc/standard/docs/access-control.md.txt).

- Learn about
  [best practices for using service accounts](https://docs.cloud.google.com/iam/docs/best-practices-service-accounts.md.txt).

- Learn how to
  [describe a trigger and verify its associated service account](https://docs.cloud.google.com/eventarc/docs/managing-triggers.md.txt#trigger-describe).