Service Management API

Related topics

• Cloud Endpoints depends on Service Management API From the official documentation: “Cloud Endpoints uses Service Management to manage your API.”
• Extensible Service Proxy V2 depends on Service Management API From the official documentation: “At a minimum, Endpoints and ESP require the following Google services to be enabled: | Name | Title | | --- | --- | | `servicemanagement.googleapis.com` | Service Management API |”
• API Gateway depends on Service Management API From the official documentation: “API Gateway requires that you enable the following Google services: | Name | Title | | --- | --- | | `apigateway.googleapis.com` | API Gateway API | | `servicemanagement.googleapis.com` | Service Management API |”
• Cloud Audit Logs works with Service Management API From the official documentation: “Cloud Audit Logs for Service Management let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Endpoints works with Service Management API From the official documentation: “To deploy the Endpoints configuration, you use the [gcloud endpoints services deploy](/sdk/gcloud/reference/endpoints/services/deploy) command. This command uses [Service Management](/service-infrastructure/docs/manage-config) to create a managed service.”
• Extensible Service Proxy depends on Service Management API From the official documentation: “Upon startup, ESP or ESPv2 obtains its service configuration from Service Management.”
• Google Cloud CLI works with Service Management API From the official documentation: “The simplest approach to using the Service Management API (other than just using the [Google Cloud console](https://console.cloud.google.com) web UI), and our recommendation for most operational use cases, is via the `gcloud` [command line…”
• Google Cloud CLI configures Service Management API From the official documentation: “You use the Google Cloud CLI to deploy your Endpoints configuration to Service Management.”
• Identity and Access Management works with Service Management API From the official documentation: “Understand and use Identity and Access Management with the Service Management API.”
• Service Management API is part of Cloud Endpoints From the official documentation: “The components that make up Endpoints are: - Extensible Service Proxy (ESP) or Extensible Service Proxy V2 (ESPv2) - for injecting Endpoints functionality. - Service Control - for applying API management rules. - Service Management - for configuring API management rules.”
• Service Management API configures Cloud Monitoring From the official documentation: “After you have authored such configuration, you will need to follow [Managing Service Configurations](/service-infrastructure/docs/manage-config) and [Managing Service Rollouts](/service-infrastructure/docs/rollout) to push the service configuration to Service Management API…”
• Service Management API depends on Identity and Access Management From the official documentation: “The Service Management API uses [Identity and Access Management](/iam) (Cloud IAM) to control access to managed services and their child resources.”
• Service Management API configures managed service From the official documentation: “The first time you deploy your service configuration, the `gcloud` command calls a Service Management API to create a managed service by using the name that you specified in the `name` field of your service configuration YAML file.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Extensible Service Proxy is an alternative to Extensible Service Proxy V2 From the official documentation: “ESPv2 is a drop-in replacement for ESP.”
• API Gateway works with Cloud Run From the official documentation: “API Gateway only supports Cloud Run gRPC services at this time.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Run works with Extensible Service Proxy V2 From the official documentation: “Deploy the ESPv2 Cloud Run service with the new image you built above.”
• Cloud Endpoints works with Compute Engine From the official documentation: “Getting started with Endpoints on Compute Engine”
• Cloud Endpoints works with GKE From the official documentation: “In addition, Endpoints only supports gRPC services for GKE, Compute Engine, and Cloud Run (Beta).”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Google Kubernetes Engine From the official documentation: “Connecting Cloud Run services to Cloud Service Mesh lets you securely route traffic to workloads on GKE.”
• 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:”
• 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.”
• Compute Engine works with Extensible Service Proxy V2 From the official documentation: “Learn how to configure, deploy, and issue requests against a sample API and ESPv2 running in Compute Engine in a Docker container.”
• Compute Engine works with Google Cloud CLI From the official documentation: “Some applications might use commands from the gcloud CLI, which is included by default in most Compute Engine images.”
• Compute Engine is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• API Gateway secures Cloud Functions From the official documentation: “Deploy an API on API Gateway to secure traffic to a Cloud Functions backend using the Google Cloud CLI.”
• 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 works with Extensible Service Proxy V2 From the official documentation: “Enabling SSL for Cloud Endpoints with ESPv2”
• 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 Logging works with Google Kubernetes Engine From the official documentation: “By default, GKE clusters send system log data and system metric data to Logging and Monitoring.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Google Kubernetes Engine From the official documentation: “When Google Kubernetes Engine (GKE) [system metrics](/kubernetes-engine/docs/how-to/configure-metrics#system-metrics) are enabled, Cloud Monitoring collects the following metrics.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Extensible Service Proxy V2 is part of Cloud Endpoints From the official documentation: “The components that make up Endpoints are: - Extensible Service Proxy (ESP) or Extensible Service Proxy V2 (ESPv2) - for injecting Endpoints functionality.”
• GKE works with Google Cloud CLI From the official documentation: “GKE manages end-user authentication for you through the Google Cloud CLI.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• API Gateway works with Cloud Audit Logs From the official documentation: “Describes the audit logs created by API Gateway as part of Cloud Audit Logs.”
• API Gateway works with Cloud Endpoints From the official documentation: “Deploying Cloud Endpoints APIs on API Gateway Describes how to try your Cloud Endpoints APIs on API Gateway.”
• API Gateway works with Cloud Functions From the official documentation: “The steps required to set up API Gateway to manage and secure a [Cloud Functions](/functions/docs) backend service are outlined in the API Gateway [Quickstarts](/api-gateway/docs/quickstarts).”
• API Gateway secures Cloud Run From the official documentation: “This page shows you how to set up API Gateway to manage and secure a [Cloud Run](/run/docs) backend service with gRPC.”
• Cloud Audit Logs works with Cloud Functions From the official documentation: “This sample demonstrates how to process Cloud Audit Logs using Cloud Functions.”
• Cloud Audit Logs works with Cloud Logging From the official documentation: “- For real-time analysis, alerting, and visualization, stream the audit logs to [Logging](/logging/docs/overview).”
• Cloud Audit Logs works with Cloud Run From the official documentation: “The sample code shows you how to read Cloud Storage events using Cloud Audit Logs in a service deployed to Cloud Run.”
• Cloud Audit Logs works with Google Kubernetes Engine From the official documentation: “For clusters on patch versions 1.21.9 and 1.22.3 or later with Cloud Logging [enabled](/stackdriver/docs/solutions/gke/installing#installing), GKE provides a [Cloud Audit Logs log](/kubernetes-engine/docs/how-to/audit-logging#viewing_your_projects_admin_activity_log) to…”
• Cloud Endpoints works with Cloud Logging From the official documentation: “With APIs deployed with Endpoints, you can monitor critical operations metrics in the Google Cloud console, and gain insight into your users and usage with Cloud Logging.”
• Cloud Endpoints works with Cloud Monitoring From the official documentation: “Metrics collected by Endpoints are also available in Cloud Monitoring.”
• Cloud Endpoints depends on Extensible Service Proxy V2 From the official documentation: “Endpoints for OpenAPI depends on either ESP or ESPv2 for API management.”
• Cloud Endpoints works with Google Kubernetes Engine From the official documentation: “Getting started with Endpoints on GKE”
• Cloud Functions works with Cloud Logging From the official documentation: “Code running in Google Cloud Functions itself writes log entries to // Cloud Logging.”
• Cloud Functions depends on Cloud Run From the official documentation: “Cloud Run functions represent the next evolution of Cloud Functions, offering an event-driven programming model with enhanced control and scalability, leveraging the Cloud Run serverless platform.”
• Cloud Functions works with Extensible Service Proxy V2 From the official documentation: “Grant ESPv2 permission to invoke your functions.”
• Cloud Functions works with Google Cloud CLI From the official documentation: “Reference for the Google Cloud CLI interface for Cloud Functions.”