If you are creating a new function, see the Console Quickstart on Cloud Run. The content on this page only applies to existing legacy functions created with the Cloud Functions v1 API.
Stay organized with collections
Save and categorize content based on your preferences.
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.
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:
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 YOUR_PROJECT_ID@appspot.gserviceaccount.com
service account.
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.
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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-17 UTC."],[[["Cloud Run functions can access most major Google Cloud services via language-specific API client libraries and/or REST APIs, including BigQuery, Bigtable, Cloud Storage, and more."],["Cloud Run functions use service accounts for authentication, providing Application Default Credentials for accessing Google Cloud APIs, with all communication encrypted in transit within Google's network."],["Cloud Run functions can be triggered by various events from services like HTTP requests, Cloud Storage, Pub/Sub, Firebase, and Cloud Logging."],["Cloud Load Balancing enables advanced network configurations for Cloud Run, including dedicated IP addresses, shared SSL certificates, and integration with services like Cloud CDN and Google Cloud Armor."],["To utilize Cloud Load Balancing security capabilities like Cloud Armor, you need to configure the ingress settings to `internal_and_gclb`, otherwise the load balancer can be bypassed."]]],[]]
