API key

Related topics

• API key is an alternative to JSON Web Token From the official documentation: “You can use a JWT token to make authenticated API proxy calls instead of using an API key.”
• API key is an alternative to service account From the official documentation: “1. Create a Service Account instead of an API key for the remote agent.”
• Secret Manager secures API key From the official documentation: “For other models, API key or bearer token that is stored as a secret in the Secret Manager can be used with the `google_ml.create_sm_secret()` SQL function.”
• API key secures API Gateway From the official documentation: “Configure API key authentication for API Gateway to secure access to your gateway using an API key, as described in the following sections.”
• API key depends on API product From the official documentation: “In Apigee, API keys are provisioned, not for APIs themselves, but for API products.”
• API key secures API product From the official documentation: “Upon registration, an app developer receives an API key that they must then include in every request to an API proxy included in the API product.”
• API key is an alternative to Application Default Credentials From the official documentation: “To use Gemini on Gemini Enterprise Agent Platform, you need to authenticate by using a [**Google Cloud API key**](/gemini-enterprise-agent-platform/models/start/api-keys) or by using [**application default credentials**](/docs/authentication/application-default-credentials).”
• API key works with Cloud Endpoints From the official documentation: “Configured your API to use an API key. This is needed for Endpoints to identify the Google Cloud project that the calling application is associated with.”
• API key works with Extensible Service Proxy From the official documentation: “If you specify an API key requirement in your service configuration, ESP uses the API key to look up the Google Cloud project that the API key is associated with.”
• Application restrictions configures API key From the official documentation: “Application restrictions specify which websites, IP addresses, or apps can use an API key.”
• Application restrictions secures API key From the official documentation: “Application restrictions specify which websites, IP addresses, or apps can use your API key.”
• VPC Service Controls secures API key From the official documentation: “To restrict API key usage to a specific network when using Private Google Access, [set up a VPC Service Controls perimeter](/vpc-service-controls/docs/set-up-service-perimeter-verify-access) instead.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Cloud Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
• Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
• Application Default Credentials secures Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• API Gateway works with Cloud Run From the official documentation: “API Gateway only supports Cloud Run gRPC services at this time.”
• Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Cloud Run functions depends on Pub/Sub From the official documentation: “The Pub/Sub message triggers Cloud Run functions.”
• Cloud Run functions works with Workflows From the official documentation: “Use Workflows with Cloud Run and Cloud Run functions tutorial”
• Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials works with Workflows From the official documentation: “To authenticate to Workflows, set up Application Default Credentials.”
• Cloud Endpoints works with Compute Engine From the official documentation: “Getting started with Endpoints on Compute Engine”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• Cloud Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Cloud Run works with Workflows From the official documentation: “Use Workflows with Cloud Run and Cloud Run functions tutorial”
• Cloud Run functions depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Compute Engine works with Extensible Service Proxy From the official documentation: “Learn how to configure, deploy, and issue requests against a sample API and ESP using an instance running in Compute Engine.”
• Pub/Sub works with Workflows From the official documentation: “Pub/Sub can be integrated into multistep serverless [Workflows](/workflows) declaratively.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• Application Default Credentials configures Cloud Run functions From the official documentation: “To authenticate to Cloud Run functions, set up Application Default Credentials.”
• Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• Application Default Credentials works with service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• Cloud Endpoints works with Cloud Run From the official documentation: “In addition, Endpoints only supports gRPC services for GKE, Compute Engine, and Cloud Run (Beta).”
• Cloud Endpoints depends on Extensible Service Proxy From the official documentation: “Endpoints for OpenAPI depends on either ESP or ESPv2 for API management.”
• Cloud Endpoints works with Extensible Service Proxy From the official documentation: “Enabling SSL with ESP Shows how to enable an SSL port for your deployed Endpoints service using ESP.”
• Cloud Endpoints depends on Identity and Access Management From the official documentation: “Endpoints uses [Identity and Access Management (IAM)](/iam/docs) to control access to your API.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• Cloud Run functions works with Secret Manager From the official documentation: “[Secret Manager](/secret-manager) stores the Cloud Run functions secrets.”
• Cloud Run functions depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
• Secret Manager works with Workflows From the official documentation: “You can use a Workflows connector to access Secret Manager within a workflow.”
• service account depends on Secret Manager From the official documentation: “Make sure that the service account that AlloyDB Omni uses has the `secretmanager.secretAccessor` permission to read the secret from Secret Manager.”
• VPC Service Controls secures Compute Engine From the official documentation: “To further protect your Compute Engine resources, you can protect them using [VPC Service Controls](/vpc-service-controls/docs/overview).”
• VPC Service Controls works with Workflows From the official documentation: “You can use VPC Service Controls with Workflows to help protect your services.”
• Workflows depends on Application Default Credentials From the official documentation: “To authenticate to Workflows, set up Application Default Credentials.”