# 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](https://developers.google.com/identity/protocols/application-default-credentials)
for your functions.

> [!NOTE]
> **Note:** All communication between Cloud Run functions and these services using [Cloud Client Libraries](https://docs.cloud.google.com/apis/docs/cloud-client-libraries.md.txt) is encrypted in transit and transmitted entirely within [Google's network](https://cloud.google.com/products/networking/).

## 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](https://docs.cloud.google.com/bigquery/docs/reference/libraries.md.txt)

- [Bigtable](https://docs.cloud.google.com/bigtable/docs/reference/libraries.md.txt)

- [Datastore](https://docs.cloud.google.com/datastore/docs/reference/libraries.md.txt)

- [Cloud DNS](https://docs.cloud.google.com/dns)

- [Cloud Firestore](https://docs.cloud.google.com/firestore)

- [Cloud Machine Learning Engine](https://docs.cloud.google.com/ml-engine)

- [Cloud Natural Language API](https://docs.cloud.google.com/natural-language/docs/reference/libraries.md.txt)

- [Pub/Sub](https://docs.cloud.google.com/pubsub/docs/reference/libraries.md.txt)

- [Resource Manager](https://docs.cloud.google.com/resource-manager/docs/libraries.md.txt)

- [Sensitive Data Protection](https://docs.cloud.google.com/sensitive-data-protection/docs/reference/libraries)

- [Spanner](https://docs.cloud.google.com/spanner/docs/reference/libraries.md.txt)

- [Speech-to-Text API](https://docs.cloud.google.com/speech-to-text/docs/reference/libraries)

- [Cloud SQL](https://docs.cloud.google.com/sql/docs/mysql/connect-functions.md.txt)

- [Cloud Storage](https://docs.cloud.google.com/storage/docs/reference/libraries.md.txt)

- [Cloud Translation API](https://docs.cloud.google.com/translate/docs/reference/libraries)

- [Cloud Vision API](https://docs.cloud.google.com/vision/docs/libraries.md.txt)

- [Video Intelligence API](https://docs.cloud.google.com/video-intelligence/docs/libraries.md.txt)

- [Firebase (DB, Storage, Analytics, Auth)](https://firebase.google.com/)

- [Error Reporting Client Libraries](https://docs.cloud.google.com/error-reporting/docs/reference/libraries.md.txt)

- [Logging Client Libraries](https://docs.cloud.google.com/logging/docs/reference/libraries.md.txt)

- [Monitoring Client Libraries](https://docs.cloud.google.com/monitoring/docs/reference/libraries.md.txt)

- [Cloud Trace](https://docs.cloud.google.com/trace)

- [Google Compute Engine](https://docs.cloud.google.com/compute)

## Supported event providers

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

- [HTTP](https://docs.cloud.google.com/functions/1stgendocs/calling/http.md.txt)---invoke functions directly via HTTP
  requests

- [Cloud Storage](https://docs.cloud.google.com/storage)

- [Pub/Sub](https://docs.cloud.google.com/pubsub)

- [Firebase (DB, Storage, Analytics, Auth)](https://firebase.google.com/)

- [Cloud Logging](https://docs.cloud.google.com/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](https://docs.cloud.google.com/docs/authentication/production) using
the `YOUR_PROJECT_ID@appspot.gserviceaccount.com`
service account.

> [!NOTE]
> **Note:** To learn more about the API client libraries provided by Google for the Node.js runtime, see [GitHub](https://github.com/GoogleCloudPlatform/google-cloud-node).

## Routing with Cloud Load Balancing

[Cloud Load Balancing](https://docs.cloud.google.com/load-balancing/docs/https/setting-up-https-serverless.md.txt)
is a separate product that enables advanced network configurations for all of
your applications running on Google Cloud.

When [HTTP(S) Load Balancing](https://docs.cloud.google.com/load-balancing/docs/negs/serverless-neg-concepts.md.txt)
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](https://docs.cloud.google.com/cdn/docs/overview.md.txt),
  [Google Cloud Armor](https://docs.cloud.google.com/armor/docs/security-policy-overview.md.txt), or
  [security policies](https://docs.cloud.google.com/load-balancing/docs/ssl-policies-concepts.md.txt).

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](https://docs.cloud.google.com/sdk/gcloud/reference/functions/deploy.md.txt#--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.