Receive direct events from Cloud Storage (Google Cloud console)

Create a Cloud Storage bucket

1. In the Google Cloud console, go to the Cloud Storage Buckets page.

   Go to Buckets

2. Click add_box Create.

3. Enter a unique Name for your bucket.

   For example, hello-bucket.

4. Click Continue.

5. For Location type, select Region, and then select us-central1 (Iowa).

6. Accept the other defaults.

7. Click Create.

After the event source is created, you can deploy the event receiver service to Cloud Run.

Deploy the event receiver service to Cloud Run

Deploy a sample Cloud Run service that receives and logs events.

1. In the Google Cloud console, go to the Cloud Run Services page.

   Go to Services

2. Click add_box Create service.

3. In the Create service form:

   1. Select Deploy one revision from an existing container image.

   2. Click Test with a sample container.

   3. In the Region list, for the location of your service, select us-central1 (Iowa).

   4. For Authentication, select Allow unauthenticated invocations.

   5. To deploy the sample container image, click Create.

The deployment of the hello service can take up to two minutes to complete.

Create an Eventarc trigger

1. In the Google Cloud console, go to the Eventarc Triggers page.

   Go to Triggers

2. Click add_box Create trigger.

3. Type a Trigger name.

   For example, hello-trigger.

4. In the Trigger type list, select Google sources.

   This filters events sent from Google Cloud providers (directly or through Cloud Audit Logs entries), or providers using Pub/Sub messages.

5. In the Event provider list, select Cloud Storage.

6. In the Event type list, select Direct > google.cloud.storage.object.v1.finalized.

7. For Bucket, select the hello-bucket Cloud Storage bucket you created previously.

8. If prompted, grant the following:

   • iam.serviceAccountTokenCreator role to Pub/Sub service account
   • pubsub.publisher role to Cloud Storage service account

9. Use the Default compute service account as the service account that invokes your service.

10. In the Event destination list, select Cloud Run.

11. For the Cloud Run service, select the sample hello service you created previously.

12. Click Create.

It might take a few minutes before all necessary permissions are propagated to the Eventarc service agent. If you receive a Permission denied while using the Eventarc Service Agent error, wait a few minutes, and then try again. Once a trigger is created, it can take up to two minutes for a trigger to be fully functional.

Generate and view an event

Generate an event and confirm that the Eventarc trigger is working as expected.

1. To generate an event:

   1. Create a text file with the filename random.txt and the text "Hello World".

   2. In the Google Cloud console, go to the Cloud Storage Buckets page.

      Go to Buckets

   3. Click the name of the storage bucket you created.

   4. In the Objects tab, click Upload files and upload the random.txt file.

   The upload generates an event and the Cloud Run service logs the event's message.

2. To view the log entry:

   1. In the Google Cloud console, go to the Cloud Run Services page.

      Go to Services

   2. Click the name of the service you created.

   3. To retrieve the log entries for all revisions of this service, in the Service details page, click the Logs tab. You can filter by log severity level.

   4. Look for a log entry similar to:

      Received event of type google.cloud.storage.object.v1.finalized. Event data: [...]

Congratulations! You have successfully deployed an event receiver service to Cloud Run, created an Eventarc trigger, generated an event from Cloud Storage, and viewed it in the Cloud Run logs.