This tutorial shows you how to deploy a containerized application using anauthenticated Cloud Run service that receives events throughEventarc.

Note: 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 allowspublic (unauthenticated) access.

By specifying filters for an Eventarc trigger, you canconfigure the routing of events, including the event source and the eventtarget. In this case, an update to a Cloud Storage bucket triggersthe event and a request is sent to your Cloud Run service inthe form of an of HTTP request.

Objectives

In this tutorial, you will:

1. Create a Cloud Storage bucket to be the event source.

2. Deploy an event receiver service to Cloud Run thatrequires authenticated invocations.

3. Create an Eventarc trigger that routes events fromthe Cloud Storage bucket to the Cloud Runservice.

4. Generate an event by uploading a file to the Cloud Storage bucketand view the event in the Cloud Run logs.

Costs

In this document, you use the following billable components of Google Cloud:

• Artifact Registry
• Cloud Build
• Cloud Run
• Cloud Storage
• Eventarc

To generate a cost estimate based on your projected usage, use thepricing calculator.

Before you begin

Security constraints defined by your organization might prevent you from completing the following steps. For troubleshooting information, seeDevelop applications in a constrained Google Cloud environment.

Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

Install the Google Cloud CLI.

If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

Toinitialize the gcloud CLI, run the following command:

gcloudinit

Create or select a Google Cloud project.

Roles required to select or create a project

• Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
• Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.create permission.Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

• Create a Google Cloud project:

  gcloud projects createPROJECT_ID

  ReplacePROJECT_ID with a name for the Google Cloud project you are creating.

• Select the Google Cloud project that you created:

  gcloud config set projectPROJECT_ID

  ReplacePROJECT_ID with your Google Cloud project name.

Verify that billing is enabled for your Google Cloud project.

Install the Google Cloud CLI.

If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

Toinitialize the gcloud CLI, run the following command:

gcloudinit

Create or select a Google Cloud project.

Roles required to select or create a project

• Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
• Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains theresourcemanager.projects.create permission.Learn how to grant roles.

Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

• Create a Google Cloud project:

  gcloud projects createPROJECT_ID

  ReplacePROJECT_ID with a name for the Google Cloud project you are creating.

• Select the Google Cloud project that you created:

  gcloud config set projectPROJECT_ID

  ReplacePROJECT_ID with your Google Cloud project name.

Verify that billing is enabled for your Google Cloud project.

1. If you are not using Cloud Shell, update the Google Cloud CLIcomponents and log in using your account:

   gcloudcomponentsupdategcloudauthlogin

2. Enable the APIs:

   gcloudservicesenableartifactregistry.googleapis.com\cloudbuild.googleapis.com\eventarc.googleapis.com\run.googleapis.com\storage.googleapis.com

3. Set the configuration variables used in this tutorial:

   exportREGION=us-central1gcloudconfigsetrun/region${REGION}gcloudconfigsetrun/platformmanagedgcloudconfigseteventarc/location${REGION}

4. You or your administrator must grant the deployer account, the trigger identity, and optionally, the Pub/Sub service agent the following IAM roles.

   Required roles for the deployer account

   1. If you are the project creator, you are granted thebasic Owner role(roles/owner). By default, this Identity and Access Management (IAM) roleincludes the permissions necessary for full access to most Google Cloudresources and you can skip this step.

      If you are not the project creator, required permissions must be granted onthe project to the appropriateprincipal. For example, a principal can bea Google Account (for end users) or a service account (for applications andcompute workloads). For more information, see theRoles and permissions pagefor your event destination.

      To get the permissions that you need to complete this tutorial, ask your administrator to grant you the following IAM roles on your project:

      • Cloud Build Editor (roles/cloudbuild.builds.editor)
      • Cloud Run Admin (roles/run.admin)
      • Cloud Run Source Developer (roles/run.sourceDeveloper)
      • Eventarc Admin (roles/eventarc.admin)
      • Logs View Accessor (roles/logging.viewAccessor)
      • Project IAM Admin (roles/resourcemanager.projectIamAdmin)
      • Service Account Admin (roles/iam.serviceAccountAdmin)
      • Service Account User (roles/iam.serviceAccountUser)
      • Service Usage Admin (roles/serviceusage.serviceUsageAdmin)
      • Storage Admin (roles/storage.admin)

      For more information about granting roles, seeManage access to projects, folders, and organizations.

      You might also be able to get the required permissions throughcustom roles or otherpredefined roles.

      Note that by default,Cloud Build permissions include permissions to upload and download Artifact Registry artifacts.

   Required roles for the trigger identity

   1. Make note of theCompute Enginedefault service account as you will you attach it to an Eventarc trigger to representthe identity of the trigger for testing purposes. This service account is automatically createdafter enabling or using a Google Cloud service that uses Compute Engine, and with thefollowing email format:

      PROJECT_NUMBER-compute@developer.gserviceaccount.com

      ReplacePROJECT_NUMBER with your Google Cloudproject number. You can find your project number on theWelcomepage of the Google Cloud console or by running the following command:

      gcloudprojectsdescribePROJECT_ID--format='value(projectNumber)'

      For production environments, we strongly recommendcreating a new service accountand granting it one or more IAM roles that contain theminimum permissions requiredand follow the principle ofleast privilege.

      Note:

      Theiam.automaticIamGrantsForDefaultServiceAccounts organization policy constraint prevents the Editor role from being automatically granted to default service accounts. If you created your organization after May 3, 2024, this constraint is enforced by default.

      We strongly recommend that you enforce this constraint to disable the automatic role grant. If you disable the automatic role grant, you must decide which roles to grant to the default service accounts, and thengrant these roles yourself.

      If the default service account already has the Editor role, we recommend that you replace the Editor role with less permissive roles.To safely modify the service account's roles, usePolicy Simulator to see the impact of the change, and thengrant and revoke the appropriate roles.

   2. By default, Cloud Run services are only callable by ProjectOwners, Project Editors, and Cloud Run Admins and Invokers.You cancontrolaccess on a per-service basis; however, for testing purposes, grant theCloud RunInvoker role (run.invoker) on the Google Cloud project to theCompute Engine service account. This grants the role on allCloud Run services and jobs in a project.

      gcloudprojectsadd-iam-policy-bindingPROJECT_ID\--member=serviceAccount:PROJECT_NUMBER-compute@developer.gserviceaccount.com\--role=roles/run.invoker

      Note that if you create a trigger for an authenticatedCloud Run service without granting the Cloud RunInvoker role, the trigger is created successfully and is active. However, thetrigger will not work as expected and a message similar to the following appearsin the logs:

      The request was not authenticated. Either allowunauthenticated invocations or set the proper Authorization header.
   3. Grant theEventarcEvent Receiver role (roles/eventarc.eventReceiver) on theproject to the Compute Engine default service account so thatthe Eventarc trigger can receive events from event providers.

      gcloudprojectsadd-iam-policy-bindingPROJECT_ID\--member=serviceAccount:PROJECT_NUMBER-compute@developer.gserviceaccount.com\--role=roles/eventarc.eventReceiver

   Optional role for the Pub/Sub service agent

   • If you enabled the Cloud Pub/Sub service agent on or before April8, 2021, to support authenticated Pub/Sub push requests, granttheServiceAccount Token Creator role (roles/iam.serviceAccountTokenCreator)to the service agent. Otherwise, this role is granted by default:

     gcloudprojectsadd-iam-policy-bindingPROJECT_ID\--member=serviceAccount:service-PROJECT_NUMBER@gcp-sa-pubsub.iam.gserviceaccount.com\--role=roles/iam.serviceAccountTokenCreator

Clean up

If you created a new project for this tutorial,delete the project.If you used an existing project and want to keep it without the changes addedin this tutorial,delete the resources created for the tutorial.

Delete the project

The easiest way to eliminate billing is to delete the project that you created for the tutorial.

To delete the project:

Caution: Deleting a project has the following effects:
• Everything in the project is deleted. If you used an existing project for the tasks in this document, when you delete it, you also delete any other work you've done in the project.
• Custom project IDs are lost. When you created this project, you might have created a custom project ID that you want to use in the future. To preserve the URLs that use the project ID, such as anappspot.com URL, delete selected resources inside the project instead of deleting the whole project.

If you plan to explore multiple architectures, tutorials, or quickstarts, reusing projects can help you avoid exceeding project quota limits.

1. In the Google Cloud console, go to theManage resources page.

   Go to Manage resources

2. In the project list, select the project that you want to delete, and then clickDelete.
3. In the dialog, type the project ID, and then clickShut down to delete the project.

Delete tutorial resources

1. Delete the Cloud Run service you deployed in this tutorial:

   gcloudrunservicesdeleteSERVICE_NAME

   WhereSERVICE_NAME is your chosen service name.

   You can also delete Cloud Run services from theGoogle Cloud console.

2. Remove any gcloud CLI default configurations you added duringthe tutorial setup.

   For example:

   gcloud config unset run/region

   or

   gcloud config unset project

3. Delete other Google Cloud resources created in this tutorial:

   • Delete the Eventarc trigger:

     gcloud eventarc triggers deleteTRIGGER_NAME

     ReplaceTRIGGER_NAME with the name of yourtrigger.
   • Delete your container image

What's next

• Create Eventarc triggers for other event types
• Build containers
• Develop Cloud Run services