[metadata]
description: Authenticate to Google Cloud using REST.
google-signin-client-id: 721724668570-nbkv1cfusk7kk4eni4pjvepaus73b13t.apps.googleusercontent.com
google-signin-scope: profile email https://www.googleapis.com/auth/developerprofiles https://www.googleapis.com/auth/developerprofiles.award https://www.googleapis.com/auth/devprofiles.full_control.firstparty
og:description: Authenticate to Google Cloud using REST.
og:image: https://docs.cloud.google.com/_static/cloud/images/social-icon-google-cloud-1200-630.png
og:image:height: 630
og:image:width: 1200
og:locale: en
og:site_name: Google Cloud Documentation
og:title: Authenticate with REST | Authentication | Google Cloud Documentation
og:type: website
og:url: https://docs.cloud.google.com/docs/authentication/rest
theme-color: #1a73e8
twitter:card: summary_large_image
viewport: width=device-width, initial-scale=1

[canonical-links]
https://docs.cloud.google.com/docs/authentication/rest

[document-links]
--impersonate-service-account flag: /sdk/gcloud/reference#--impersonate-service-account
/
/: https://docs.cloud.google.com/s/results
2-step verification requirement: /docs/authentication/mfa-requirement
AI and ML: /docs/ai-ml
AI and ML: https://docs.cloud.google.com/docs/ai-ml
About Google: //about.google/
Access and resources management: /docs/access-resources
Access and resources management: https://docs.cloud.google.com/docs/access-resources
Apache 2.0 License: https://www.apache.org/licenses/LICENSE-2.0
App Engine flexible environment: /appengine/docs/flexible/python/runtime#metadata_server
App Engine standard environment: /appengine/docs/standard/python3/runtime#metadata_server
Application Default Credentials: /docs/authentication/application-default-credentials
Application development: /docs/application-development
Application development: https://docs.cloud.google.com/docs/application-development
Application hosting: /docs/application-hosting
Application hosting: https://docs.cloud.google.com/docs/application-hosting
Authenticate by using service account impersonation: /docs/authentication/use-service-account-impersonation
Authenticate for the gcloud CLI: /sdk/docs/authenticate
Authenticate for using REST: /docs/authentication/rest
Authenticate for using client libraries: /docs/authentication/client-libraries
Authenticate using client libraries: /docs/authentication/client-libraries
Authentication methods at Google: /docs/authentication
Authentication use cases: /docs/authentication/use-cases
Authentication: https://docs.cloud.google.com/docs/authentication
Best practices for managing API keys: /docs/authentication/api-keys-best-practices
Blog: //cloud.google.com/blog/
Browser role: /iam/docs/roles-permissions/browser
Client libraries and Cloud APIs explained: /apis/docs/client-libraries-explained
Client libraries best practices: /apis/docs/client-libraries-best-practices
Cloud Architecture Center: /architecture/
Cloud Build: /build/docs/securing-builds/authorize-service-to-service-access
Cloud Client Libraries overview: /apis/docs/cloud-client-libraries
Cloud Run functions: /functions/docs/securing/function-identity#metadata-server
Cloud Run: /run/docs/container-contract#metadata-server
Cloud-based development environment: /docs/authentication/set-up-adc-cloud-dev-environment
Code samples: /docs/samples
Community forums: //discuss.google.dev/c/google-cloud/14/
Compute Engine: /compute/docs/instances/verifying-instance-identity#request_signature
Compute: /docs/compute-area
Compute: https://docs.cloud.google.com/docs/compute-area
Configure the gcloud CLI for use behind a proxy or firewall: /sdk/docs/proxy-settings
Console: //console.cloud.google.com/
Contact sales: //cloud.google.com/contact/
Containerized environment: /docs/authentication/set-up-adc-containerized-environment
Costs and usage management: /docs/costs-usage
Costs and usage management: https://docs.cloud.google.com/docs/costs-usage
Create a short-lived access token: /iam/docs/create-short-lived-credentials-direct#sa-credentials-oauth
Creative Commons Attribution 4.0 License: https://creativecommons.org/licenses/by/4.0/
Cross-product tools: /docs/cross-product-overviews
Cross-product tools: https://docs.cloud.google.com/docs/cross-product-overviews
Data analytics and pipelines: /docs/data
Data analytics and pipelines: https://docs.cloud.google.com/docs/data
Databases: /docs/databases
Databases: https://docs.cloud.google.com/docs/databases
Developer tools: https://docs.cloud.google.com/docs/costs-usage
Distributed, hybrid, and multicloud: /docs/dhm-cloud
Distributed, hybrid, and multicloud: https://docs.cloud.google.com/docs/dhm-cloud
Documentation: https://docs.cloud.google.com/docs
Enable accessibility features: /sdk/docs/enabling-accessibility-features
Events: //cloud.google.com/events/
Get an ID token: /docs/authentication/get-id-token
Getting Started with Google Cloud: /docs/get-started/
GitHub: //github.com/googlecloudPlatform/
Google Cloud Marketplace: //cloud.google.com/marketplace/
Google Cloud SDK overview: /sdk/docs/overview
Google Cloud SDK: https://docs.cloud.google.com/sdk/docs
Google Cloud Tech on YouTube: //www.youtube.com/googlecloudplatform
Google Cloud on YouTube: //www.youtube.com/googlecloud
Google Cloud pricing: //cloud.google.com/pricing/
Google Cloud terms: //cloud.google.com/product-terms
Google Developers Site Policies: https://developers.google.com/site-policies
Google Kubernetes Engine: /kubernetes-engine/docs/concepts/workload-identity#instance_metadata
Guides: /sdk/docs/overview
Guides: https://docs.cloud.google.com/sdk/docs/overview
Home: https://docs.cloud.google.com/
How Application Default Credentials works: /docs/authentication/application-default-credentials
Identity management products: /docs/authentication/identity-products
Industry solutions: /docs/industry
Industry solutions: https://docs.cloud.google.com/docs/industry
Infrastructure as code: /docs/iac
Infrastructure as code: https://docs.cloud.google.com/docs/iac
Initialize the gcloud CLI: /sdk/docs/initialize
Install the gcloud CLI: /sdk/docs/install-sdk
Install: /sdk/docs/install
Learn how to grant roles: /iam/docs/granting-changing-revoking-access
Local development environment: /docs/authentication/set-up-adc-local-dev-environment
Manage API keys: /docs/authentication/api-keys
Manage gcloud CLI configurations: /sdk/docs/configurations
Manage gcloud CLI properties: /sdk/docs/properties
Managing gcloud CLI components: /sdk/docs/components
Migrate to the :stable image: /sdk/docs/migrate-docker-images
Migration: /docs/migration
Migration: https://docs.cloud.google.com/docs/migration
Networking: /docs/networking
Networking: https://docs.cloud.google.com/docs/networking
Observability and monitoring: /docs/observability
Observability and monitoring: https://docs.cloud.google.com/docs/observability
On-premises or another cloud provider: /docs/authentication/set-up-adc-on-premises
Our third decade of climate action: join us: //cloud.google.com/sustainability
Overview: /docs/authentication/provide-credentials-adc
Overview: /docs/authentication/tokens
Overview: /sdk/docs
Overview: /sdk/docs/downloads-docker
Overview: https://docs.cloud.google.com/sdk/docs
Privacy: //policies.google.com/privacy
Provide credentials to ADC: /docs/authentication/provide-credentials-adc
Reauthentication: /docs/authentication/reauthentication
Reference: /sdk/docs/libraries-reference
Reference: https://docs.cloud.google.com/sdk/docs/libraries-reference
Release Notes: //docs.cloud.google.com/release-notes
Resource with an attached service account: /docs/authentication/set-up-adc-attached-service-account
Resources: /sdk/docs/resources
Resources: https://docs.cloud.google.com/sdk/docs/resources
SDK, languages, frameworks, and tools: /docs/devtools
SDK, languages, frameworks, and tools: https://docs.cloud.google.com/docs/devtools
Scripting gcloud CLI commands: /sdk/docs/scripting-gcloud
Security: /docs/security
Security: https://docs.cloud.google.com/docs/security
See all products: //cloud.google.com/products/
Set up ADC for a resource with an attached service account: /docs/authentication/set-up-adc-attached-service-account
Setting required permissions: /iam/docs/create-short-lived-credentials-direct#sa-credentials-permissions
Site terms: //policies.google.com/terms?hl=en
Start free: //console.cloud.google.com/freetrial
Storage: /docs/storage
Storage: https://docs.cloud.google.com/docs/storage
Subscribe: //cloud.google.com/newsletter/
Support: //cloud.google.com/support-hub/
System status: //status.cloud.google.com
Technology areas: /docs
Technology areas: https://docs.cloud.google.com/docs
Token types: /docs/authentication/token-types
Training and Certification: //cloud.google.com/learn/training/
Troubleshoot your ADC setup: /docs/authentication/troubleshoot-adc
Uninstalling the gcloud CLI: /sdk/docs/uninstall-cloud-sdk
Use API keys to access APIs: /docs/authentication/api-keys-use
Use service account impersonation: /docs/authentication/use-service-account-impersonation
Use the Cloud CLI remote MCP server: /sdk/use-gcloud-mcp
User credentials not working: /docs/authentication/troubleshoot-adc#user-creds-client-based
Using Homebrew: /sdk/docs/downloads-homebrew
Using a snap package: /sdk/docs/downloads-snap
Using the installer: /sdk/docs/downloads-interactive
Using versioned archives: /sdk/docs/downloads-versioned-archives
X (Twitter): //x.com/googlecloud
authentication: /docs/authentication
client libraries: /docs/authentication/client-libraries
documents.analyzeEntities: /natural-language/docs/reference/rest/v1/documents/analyzeEntities
gcloud CLI authentication configuration and ADC configuration: /docs/authentication/provide-credentials-adc#gcloud-credentials
gcloud CLI cheat sheet: /sdk/docs/cheatsheet
gcloud CLI overview: /sdk/gcloud
gcloud auth application-default print-access-token command: /sdk/gcloud/reference/auth/application-default/print-access-token
gcloud auth print-access-token command: /sdk/gcloud/reference/auth/print-access-token
https://docs.cloud.google.com/docs/authentication
initialize: /sdk/docs/initializing
sign in to the gcloud CLI with your federated identity: /iam/docs/workforce-log-in-gcloud

[structured-data]
{"@context":"https://schema.org","@type":"Article","headline":"Authenticate with REST"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","item":"https://docs.cloud.google.com/sdk/docs","name":"Google Cloud SDK","position":1},{"@type":"ListItem","item":"https://docs.cloud.google.com/docs/authentication","name":"Authentication","position":2},{"@type":"ListItem","item":"https://docs.cloud.google.com/docs/authentication/rest","name":"Authenticate with REST","position":3}]}

[content]
Authenticate with REST | Authentication | Google Cloud Documentation
Skip to main content
Technology areas
close
AI and ML
Application development
Application hosting
Compute
Data analytics and pipelines
Databases
Distributed, hybrid, and multicloud
Industry solutions
Migration
Networking
Observability and monitoring
Security
Storage
Cross-product tools
close
Access and resources management
Costs and usage management
Infrastructure as code
SDK, languages, frameworks, and tools
/
Console
English
Deutsch
Español
Español – América Latina
Français
Indonesia
Italiano
Português
Português – Brasil
עברית
中文 – 简体
中文 – 繁體
日本語
한국어
Sign in
Google Cloud SDK
Authentication
Start free
Overview
Guides
Reference
Resources
Technology areas
More
Overview
Guides
Reference
Resources
Cross-product tools
More
Console
Discover
Google Cloud SDK overview
gcloud CLI overview
Cloud Client Libraries overview
Client libraries and Cloud APIs explained
Get started
Install the gcloud CLI
Cloud CLI Remote MCP Server
Use the Cloud CLI remote MCP server
Other installation methods
Using Docker
Overview
Migrate to the :stable image
Using a snap package
Using versioned archives
Using the installer
Using Homebrew
Authenticate to Google Cloud
Authentication methods at Google
Ways to authenticate
Authenticate for using client libraries
Authenticate for using REST
Authenticate by using service account impersonation
Application Default Credentials
Set up Application Default Credentials
Overview
Local development environment
Resource with an attached service account
Containerized environment
On-premises or another cloud provider
Cloud-based development environment
How Application Default Credentials works
Troubleshoot your ADC setup
API keys
Use API keys to access APIs
Manage API keys
Best practices for managing API keys
Get an ID token
Tokens
Overview
Token types
2-step verification requirement
Reauthentication
Authentication use cases
Identity management products
Configure the gcloud CLI
Initialize the gcloud CLI
Authenticate for the gcloud CLI
Configure the gcloud CLI for use behind a proxy or firewall
Manage gcloud CLI configurations
Manage gcloud CLI properties
Enable accessibility features
Develop
gcloud CLI cheat sheet
Scripting gcloud CLI commands
Client libraries best practices
Manage packages in gcloud CLI
Managing gcloud CLI components
Uninstalling the gcloud CLI
AI and ML
Application development
Application hosting
Compute
Data analytics and pipelines
Databases
Distributed, hybrid, and multicloud
Industry solutions
Migration
Networking
Observability and monitoring
Security
Storage
Access and resources management
Costs and usage management
Infrastructure as code
SDK, languages, frameworks, and tools
Home
Documentation
Developer tools
Google Cloud SDK
Authentication
Guides
Send feedback
Authenticate with REST
Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to authenticate when you make a REST request to a Google API.
For information about how to authenticate when you use Google client libraries, see
Authenticate using client libraries
.
Before you begin
To run the samples on this page, complete the following steps:
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
.
To
initialize
the gcloud CLI, run the following command:
gcloud
init
Enable the Cloud Resource Manager and Identity and Access Management (IAM) APIs:
Roles required to enable APIs
To enable APIs, you need the
serviceusage.services.enable
permission. If you created the project, then you likely already have this permission through the Owner role (
roles/owner
). Otherwise, you can get this permission through the Service Usage Admin role (
roles/serviceusage.serviceUsageAdmin
).
Learn how to grant roles
.
gcloud
services
enable
cloudresourcemanager.googleapis.com
iam.googleapis.com
If you don't want to use the gcloud CLI, you can skip these steps and use
service account impersonation
or
the metadata server
to generate a token.
Types of credentials
You can use the following types of credentials to authenticate a REST call:
Your
gcloud CLI credentials
.
This approach is the easiest and most secure way to provide credentials to a REST method in a local development environment. If your user account has the necessary Identity and Access Management (IAM) permissions for the method you want to call, this is the preferred approach.
Your gcloud credentials are not the same as the credentials you provide to ADC using the gcloud CLI. For more information, see
gcloud CLI authentication configuration and ADC configuration
.
The
credentials provided to Application Default Credentials (ADC)
.
This method is the preferred option for authenticating a REST call in a production environment, because ADC finds credentials from the resource where your code is running (such as a Compute Engine virtual machine). You can also use ADC to authenticate in a local development environment. In this scenario, the gcloud CLI creates a file that contains your credentials in your local file system.
The
credentials provided by impersonating a service account
.
This method requires more setup. If you want to use your existing credentials to obtain short-lived credentials for another service account, such as testing with a service account locally or requesting temporary elevated privileges, use this approach.
The
credentials returned by the metadata server
.
This method works only in environments with access to a metadata server. The credentials returned by the metadata server are the same as the credentials that would be found by
Application Default Credentials
using the attached service account, but you explicitly request the access token from the metadata server and then provide it with the REST request. Querying the metadata server for credentials requires an HTTP GET request; this method does not rely on the Google Cloud CLI.
API keys
You can use an API key with a REST request only for APIs that accepts API keys. In addition, the API key must not be restricted to prevent it from being used with the API.
gcloud CLI credentials
To run the following example, you need the
resourcemanager.projects.get
permission on the project. The
resourcemanager.projects.get
permission is included in a variety of roles—for example, the
Browser role
(
roles/browser
).
Use the
gcloud auth print-access-token
command
to insert an access token generated from your user credentials.
The following example gets details for the specified project. You can use the same pattern for any REST request.
Before using any of the request data, make the following replacements:
PROJECT_ID
: Your Google Cloud project ID or name.
To send your request, choose one of these options:
curl
Execute the following command:
curl -X GET \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
"https://cloudresourcemanager.googleapis.com/v3/projects/
PROJECT_ID
"
PowerShell
Execute the following command:
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }
Invoke-WebRequest `
-Method GET `
-Headers $headers `
-Uri "https://cloudresourcemanager.googleapis.com/v3/projects/
PROJECT_ID
" | Select-Object -Expand Content
The details for your project are returned.
For APIs that require a quota project, you must set one explicitly for the request. For more information, see
Set the quota project with a REST request
on this page.
Application Default Credentials
To run the following example, the principal associated with the credentials you provide to ADC needs the
resourcemanager.projects.get
permission on the project. The
resourcemanager.projects.get
permission is included in a variety of roles—for example, the
Browser role
(
roles/browser
).
Provide credentials to ADC
.
If you are running on a Google Cloud compute resource, you shouldn't provide your user credentials to ADC. Instead, use the attached service account to provide credentials. For more information, see
Set up ADC for a resource with an attached service account
.
Use the
gcloud auth application-default print-access-token
command
to insert the access token returned by ADC into your REST request.
The following example gets details for the specified project. You can use the same pattern for any REST request.
Before using any of the request data, make the following replacements:
PROJECT_ID
: Your Google Cloud project ID or name.
To send your request, choose one of these options:
curl
Execute the following command:
curl -X GET \
-H "Authorization: Bearer $(gcloud auth application-default print-access-token)" \
"https://cloudresourcemanager.googleapis.com/v3/projects/
PROJECT_ID
"
PowerShell
Execute the following command:
$cred = gcloud auth application-default print-access-token
$headers = @{ "Authorization" = "Bearer $cred" }
Invoke-WebRequest `
-Method GET `
-Headers $headers `
-Uri "https://cloudresourcemanager.googleapis.com/v3/projects/
PROJECT_ID
" | Select-Object -Expand Content
The details for your project are returned.
If your request returns an error message about end-user credentials not being supported by this API, see
Set the quota project with a REST request
on this page.
Impersonated service account
The simplest way to impersonate a service account to generate an access token is by using the gcloud CLI. However, if you need to generate the token programmatically, or you don't want to use the gcloud CLI, you can use impersonation to generate a short-lived token.
For more information about impersonating a service account, see
Use service account impersonation
.
Review the required permissions.
The prinicipal you want to use to perform the impersonation must have the
iam.serviceAccounts.getAccessToken
permission on the impersonated service account (also called the
privilege-bearing service account
). The
iam.serviceAccounts.getAccessToken
permission is included in the Service Account Token Creator role (
roles/iam.serviceAccountTokenCreator
). If you are using your user account, you need to add this permission even if you have the Owner role (
roles/owner
) on the project. For more information, see
Setting required permissions
.
Identify or create the privilege-bearing service account—the service account you will impersonate.
The privilege-bearing service account must have the permissions required to make the API method call.
gcloud
Use the
gcloud auth print-access-token
command
with the
--impersonate-service-account
flag
to insert an access token for the privilege-bearing service account into your REST request.
The following example gets details for the specified project. You can use the same pattern for any REST request.
To run this example, the service account you impersonate needs the
resourcemanager.projects.get
permission. The
resourcemanager.projects.get
permission is included in a variety of roles—for example, the
Browser role
(
roles/browser
).
Make the following replacements:
PRIV_SA
: The email address of the privilege-bearing service account. For example,
my-sa@my-project.iam.gserviceaccount.com
.
PROJECT_ID
: Your Google Cloud project ID or name.
curl
-X
GET
\
-H
"Authorization: Bearer
$(
gcloud
auth
print-access-token
--impersonate-service-account
=
PRIV_SA
)
"
\
"https://cloudresourcemanager.googleapis.com/v3/projects/
PROJECT_ID
"
Short-lived token
To generate a short-lived token by using service account impersonation, follow the instructions provided in
Create a short-lived access token
.
Metadata server
To get an access token from the metadata server, you must make the REST call using one of the services that has access to a metadata server:
Compute Engine
App Engine standard environment
App Engine flexible environment
Cloud Run functions
Cloud Run
Google Kubernetes Engine
Cloud Build
You use a command-line tool such as
curl
to get an access token, and then insert it into your REST request.
Query the metadata server for an access token:
curl
"http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token"
\
-H
"Metadata-Flavor: Google"
The request returns a response similar to the following example:
{
"access_token"
:
"ya29.AHES6ZRN3-HlhAPya30GnW_bHSb_QtAi85nHq39HE3C2LTrCARA"
,
"expires_in"
:
3599
,
"token_type"
:
"Bearer"
}
Insert the access token into your REST request, making the following replacements:
ACCESS_TOKEN
: The access token returned in the previous step.
PROJECT_ID
: Your Google Cloud project ID or name.
curl
-X
GET
\
-H
"Authorization: Bearer
ACCESS_TOKEN
"
\
"https://cloudresourcemanager.googleapis.com/v3/projects/
PROJECT_ID
"
API keys
To include an API key with a REST API call, use the
x-goog-api-key
HTTP header, as shown in the following example:
curl -X POST \ -H "X-goog-api-key:
API_KEY
" \ -H "Content-Type: application/json; charset=utf-8" \ -d @request.json \ "https://translation.googleapis.com/language/translate/v2"
If you can't use the HTTP header, you can use the
key
query parameter. However, this method includes your API key in the URL, exposing your key to theft through URL scans.
The following example shows how to use the
key
query parameter with a Cloud Natural Language API request for
documents.analyzeEntities
. Replace
API_KEY
with the key string of your API key.
POST https://language.googleapis.com/v1/documents:analyzeEntities?key=
API_KEY
Set the quota project with a REST request
To call some APIs with user credentials, you must also set the project that is billed for your usage and used to track quota. If your API call returns an error message saying that user credentials are not supported, or that the quota project is not set, you must explicitly set the quota project for the request. To set the quota project, include the
x-goog-user-project
header with your request.
For more information about when you might encounter this issue, see
User credentials not working
.
You must have the
serviceusage.services.use
IAM permission for a project to be able to designate it as your billing project. The
serviceusage.services.use
permission is included in the Service Usage Consumer IAM role. If you don't have the
serviceusage.services.use
permission for any project, contact your security administrator or a project owner who can give you the Service Usage Consumer role in the project.
The following example uses the Cloud Translation API to translate the word "
hello
" into Spanish. The Cloud Translation API is an API that needs a quota project to be specified. To run the sample, create a file named
request.json
with the request body content.
Before using any of the request data, make the following replacements:
PROJECT_ID
: The ID or name of the Google Cloud project to use as a billing project.
Request JSON body:
{ "q": "hello", "source": "en", "target": "es" }
To send your request, choose one of these options:
curl
Save the request body in a file named
request.json
, and execute the following command:
curl -X POST \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
-H "x-goog-user-project:
PROJECT_ID
" \
-H "Content-Type: application/json; charset=utf-8" \
-d @request.json \
"https://translation.googleapis.com/language/translate/v2"
PowerShell
Save the request body in a file named
request.json
, and execute the following command:
$cred = gcloud auth print-access-token
$headers = @{ "Authorization" = "Bearer $cred"; "x-goog-user-project" = "
PROJECT_ID
" }
Invoke-WebRequest `
-Method POST `
-Headers $headers `
-ContentType: "application/json; charset=utf-8" `
-InFile request.json `
-Uri "https://translation.googleapis.com/language/translate/v2" | Select-Object -Expand Content
The translation request succeeds. You can try the command without the
x-goog-user-project
HTTP header to see what happens when you do not specify the billing project.
What's next
See an overview of
authentication
.
Learn how to authenticate with
client libraries
.
Understand
gcloud CLI authentication configuration and ADC configuration
.
Send feedback
Except as otherwise noted, the content of this page is licensed under the
Creative Commons Attribution 4.0 License
, and code samples are licensed under the
Apache 2.0 License
. For details, see the
Google Developers Site Policies
. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-07-29 UTC.
Products and pricing
See all products
Google Cloud pricing
Google Cloud Marketplace
Contact sales
Support
Community forums
Support
Release Notes
System status
Resources
GitHub
Getting Started with Google Cloud
Code samples
Cloud Architecture Center
Training and Certification
Engage
Blog
Events
X (Twitter)
Google Cloud on YouTube
Google Cloud Tech on YouTube
About Google
Privacy
Site terms
Google Cloud terms
Manage cookies
Our third decade of climate action: join us
Sign up for the Google Cloud newsletter
Subscribe
English
Deutsch
Español
Español – América Latina
Français
Indonesia
Italiano
Português
Português – Brasil
עברית
中文 – 简体
中文 – 繁體
日本語
한국어
