Supported Services

Access Google Cloud APIs from Cloud Run functions by using a service account to act on your behalf. The service account provides Application Default Credentials for your functions.

Note: All communication between Cloud Run functions and these services using Cloud Client Libraries is encrypted in transit and transmitted entirely within Google's network.

Supported APIs

Cloud Run functions can access most major Google Cloud services via language-specific API client libraries and/or REST APIs, including the following:

• BigQuery

• Bigtable

• Cloud Data Loss Prevention

• Datastore

• Cloud DNS

• Cloud Firestore

• Cloud Machine Learning Engine

• Cloud Natural Language API

• Pub/Sub

• Resource Manager

• Spanner

• Speech-to-Text API

• Cloud SQL

• Cloud Storage

• Cloud Translation API

• Cloud Vision API

• Video Intelligence API

• Firebase (DB, Storage, Analytics, Auth)

• Error Reporting Client Libraries

• Logging Client Libraries

• Monitoring Client Libraries

• Cloud Trace

• Google Compute Engine

Supported event providers

Cloud Run functions can be triggered by events provided by the following services:

• HTTP—invoke functions directly via HTTP requests

• Cloud Storage

• Pub/Sub

• Firebase (DB, Storage, Analytics, Auth)

• Cloud Logging

Using services with Cloud Run functions

Google API Client Libraries that use application default credentials automatically obtain the built-in service account credentials from the Cloud Run functions host at runtime. By default, the client authenticates using the [e-mail] service account.

Note: To learn more about the API client libraries provided by Google for the Node.js runtime, see GitHub.

Routing with Cloud Load Balancing

Cloud Load Balancing is a separate product that enables advanced network configurations for all of your applications running on Google Cloud.

When HTTP(S) Load Balancing is enabled for serverless apps, you can:

• Configure your serverless app to serve from a dedicated IPv4 and/or IPv6 IP address that is not shared with other services.

• Reuse the same SSL certificates and private keys that you use for Compute Engine, Google Kubernetes Engine, and Cloud Storage. This eliminates the need to manage separate certificates for serverless apps.

• Use additional services that integrate with Cloud Load Balancing such as Cloud CDN, Google Cloud Armor, or security policies.

Note the following limitation and recommendations:

• To use Cloud Load Balancing-enabled security capabilities such as Cloud Armor or security policies, you must change the ingress settings to be internal_and_gclb. Users who already have the Cloud Run functions's default URL can otherwise bypass the load balancer and go directly to the function's URL.

• Support for Identity-Aware Proxy integrated with Cloud Load Balancing for Cloud Run functions is not available.