이 페이지는 Google Cloud 프로젝트에서 서비스를 사용 설정 및 중지하는 방법을 설명합니다.
서비스 사용량을 사용하여 공개 Google Cloud 서비스 및 Cloud Endpoints를 사용하여 생성된 비공개 서비스를 포함하여 프로젝트에 사용 가능한 모든 서비스를 사용 설정 또는 중지할 수 있습니다. 공개 API 및 서비스와 비공개 API 및 서비스의 차이점에 대한 자세한 내용은 공개 및 비공개 서비스를 참조하세요.
대부분의 운영 사용 사례에서 서비스를 사용 설정 및 중지하는 가장 간단한 방법은 Google Cloud 콘솔을 사용하는 것입니다. 스크립트를 작성해야 하는 경우 Google Cloud CLI를 사용할 수도 있습니다. Service Usage API와 달리 프로그래밍해야 하는 경우에는 제공된 클라이언트 라이브러리 중에 하나를 사용하는 것이 좋습니다. API를 실험하려면 이 가이드의 대체 안내를 따르고 curl 명령어를 사용하여 전체 애플리케이션 개발 환경을 설정하지 않고 API를 테스트할 수 있습니다.
시작하기 전에
API 및 서비스를 사용 설정하고 중지하려면 다음 사항이 필요합니다.
Google Cloud 프로젝트 Google Cloud 프로젝트를 만드는 방법은 프로젝트 만들기 및 관리를 참조하세요.
services.enable 메서드는 서버에서 진행 중인 작업을 나타내는 장기 실행 작업 리소스를 반환합니다. 각 작업에는 고유한 리소스 이름이 있습니다. 예를 들어 다음은 이름이 operations/acf.2e2fcfce-8327-4984-9040-a67777082687인 작업입니다.
프로젝트에 여러 API 서비스를 사용 설정하려면 각 API 서비스에 대해 사용 설정 명령어를 하나씩 실행하거나, 일괄 작업 사용 설정 명령어를 실행하고 여러 API를 지정할 수 있습니다. 예를 들어 프로젝트에서 Pub/Sub 및 Dataflow API 서비스를 모두 사용 설정하려면 다음 안내를 따르세요.
서비스를 사용 중지하면 serviceusage.googleapis.com/mutate_requests 할당량 측정항목의 할당량이 사용됩니다. 사용 가능한 기본 할당량은 초당 쿼리 수(QPS) 2개입니다.
API는 언제든지 프로젝트에서 사용 중지할 수 있습니다. 단, 미결제 비용은 계정으로 청구되며 프로젝트에서 청구 가능한 API 사용에 대해서도 요금이 부과됩니다. 자세한 내용은 API 및 결제를 참조하세요.
Cloud Storage 및 BigQuery와 같은 많은 서비스에서 데이터 저장 요금이 청구됩니다. 서비스의 API 액세스를 중지해도 기본 데이터는 삭제되지 않고 계속 요금이 청구됩니다. 서비스 사용을 중단하고 이후 요금이 발생하지 않도록 하려면 서비스의 API 액세스를 중지하기 전에 서비스와 연결된 모든 데이터를 삭제해야 합니다.
GKE API를 사용 중지하면 프로젝트에서 실행 중인 클러스터가 정지됩니다. 30일 후에는 정지된 클러스터가 삭제됩니다. 정지된 클러스터를 복구하려면 GKE API를 사용 설정하세요. 클러스터가 복구되기까지 최대 24시간이 걸릴 수 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-21(UTC)"],[],[],null,["# Enabling and Disabling Services\n===============================\n\nThis page describes how to enable and disable services for a Google Cloud project.\nYou can use Service Usage to enable or disable any available service\nfor your projects, including public\n[Google Cloud services](/terms/services) and private services created\nusing [Cloud Endpoints](/endpoints/docs). For more information on the\ndifferences between public and private APIs and services, see\n[Public and Private Services](/service-usage/docs/public-vs-private).\n\nFor most operational use cases, the simplest way to enable and disable services\nis to use the Google Cloud console. If you need to create scripts, you can also use the\nGoogle Cloud CLI. If you need to program against the\nService Usage API, we recommend that you use one of our provided\n[client libraries](/service-usage/docs/libraries). To experiment with the API,\nyou can follow the alternative instructions in this guide and use the `curl`\ncommand to test the API without setting up a full application development\nenvironment.\n\nBefore you begin\n----------------\n\nTo enable and disable APIs and services you need:\n\n- A Google Cloud project. To learn how to create a Google Cloud project, see [Creating and Managing Projects](/resource-manager/docs/creating-managing-projects).\n- The correct [Identity and Access Management](/iam) permissions. To learn about the IAM requirements for Service Usage, see [Access Control](/service-usage/docs/access-control).\n- To install the [Google Cloud CLI](/sdk/docs/install).\n- If you want to use the `curl` examples in this guide, make sure you follow the instructions to complete the initial setup in [Getting Started](/service-usage/docs/set-up-development-environment). These steps include defining `gcurl`, which is an authenticated alias for the standard `curl` command, and defining the environment variable `PROJECT_NUMBER`.\n\nEnabling services\n-----------------\n\nEnabling services uses quota from the\n`serviceusage.googleapis.com/mutate_requests` quota metric. The default\navailable quota is 2 queries per second (QPS). \n\n### console\n\nTo enable an API for a project:\n\n1. Go to the Google Cloud console [API Library](https://console.cloud.google.com/project/_/apis/library) page. \n [Go to the API Library page](https://console.cloud.google.com/project/_/apis/library)\n2. Select the Google Cloud project where you want to enable\n an API by performing one of the following:\n\n - Click on a Google Cloud project under **Select a recent project**.\n\n - Use the Google Cloud project browser by performing the following\n steps:\n\n 1. Click **Select project** to open the Google Cloud project browser.\n 2. Find your project and then click on the Google Cloud project name.\n 3. Click **Open** to open the project.\n3. Click the API you want to enable. If you need help finding the API, use\n the **Search for APIs \\& Services** box near the top of the page. A page\n describing the API appears.\n\n4. Click the **Enable** button.\n\n### gcloud\n\nRun the following command to enable the Pub/Sub API service in your\ncurrent project: \n\n```\ngcloud services enable pubsub.googleapis.com\n```\n\nThe command produces output similar to the following: \n\n```\nWaiting for async operation operations/acf.2e2fcfce-8327-4984-9040-a67777082687 to complete...\nOperation finished successfully.\n```\n\nYou can use the following command to get the operation details: \n\n```\ngcloud services operations describe operations/acf.2e2fcfce-8327-4984-9040-a67777082687\n```\n\n### curl\n\nYou can enable a single service using the\n[`services.enable`](/service-usage/docs/reference/rest/v1/services/enable)\nmethod. You can enable between 2 and 20 services in a single operation using\nthe [`services.batchEnable`](/service-usage/docs/reference/rest/v1/services/batchEnable)\nmethod.\n\n### Enable a single service\n\nThe following command enables the Pub/Sub API service on your\nproject: \n\n gcurl -d '{}' \"https://serviceusage.googleapis.com/v1/projects/${PROJECT_NUMBER}/services/pubsub.googleapis.com:enable\"\n\nThe\n[`services.enable`](/service-usage/docs/reference/rest/v1/services/enable)\nmethod returns a\n[Long Running Operation](/service-usage/docs/reference/rest/v1/operations)\nresource, which represents ongoing work on the server. Each operation has\na unique resource name. For example, here is an operation\nwith the name `operations/acf.2e2fcfce-8327-4984-9040-a67777082687`: \n\n {\n \"name\": \"operations/acf.2e2fcfce-8327-4984-9040-a67777082687\"\n }\n\nTo poll the operation status by using the Service Usage\n[`operations.get`](/service-usage/docs/reference/rest/v1/operations/get)\nmethod, pass the name of the operation to the API: \n\n OPERATION_NAME=\"operations/acf.2e2fcfce-8327-4984-9040-a67777082687\"\n gcurl \"https://serviceusage.googleapis.com/v1/${OPERATION_NAME}\"\n\n### Enable multiple services at once\n\nIf you want to enable multiple API services on your project, you can issue\nan enable command for each API service individually, or you can issue one\nbatch enable command and specify multiple APIs. For example, to enable both\nthe Pub/Sub and Dataflow API services on your project: \n\n gcurl -d '{\n \"serviceIds\": [\"pubsub.googleapis.com\", \"dataflow.googleapis.com\"]\n }' \"https://serviceusage.googleapis.com/v1/projects/${PROJECT_NUMBER}/services:batchEnable\"\n\nLike `services.enable`, [`services.batchEnable`](/service-usage/docs/reference/rest/v1/services/batchEnable)\nreturns an operation resource, which you can poll by using its `name`.\n| **Note:** The process for enabling APIs can vary. Some APIs prompt you to accept their Terms of Service before you can enable them. Some APIs are in preview mode and require special signup and whitelisting before you can use them. Other APIs might ask for additional information, such as your organization's contact information and the name of the application you are developing. When more information is requested, it will not be shared outside of Google; it's used to help Google understand how the API is being used and as a secondary contact should we need to contact you regarding your use of the service.\n\nDisabling services\n------------------\n\nDisabling services uses quota from the\n`serviceusage.googleapis.com/mutate_requests` quota metric. The default\navailable quota is 2 queries per second (QPS).\n\nYou can disable an API for a project at any time, although any pending fees will\nstill be charged to your account and you'll be charged for any billable API use\nin your projects. For more information, see\n[APIs and Billing](https://support.google.com/cloud/answer/6158867).\n\nMany services like Cloud Storage and BigQuery charge to store data. Disabling a\nservice's API access does not delete the underlying data which will continue\nto be billed. If your intent is to discontinue using a service and stop all\nfuture charges, be sure to delete all data associated with the service before\ndisabling the service's API access.\n\nIf you disable the GKE API, any running clusters in the project become suspended. After 30 days, the suspended clusters are deleted. To reinstate your suspended clusters, enable the GKE API. It may take up to 24 hours for the clusters to be reinstated.\n**Note:** In v1 of the API, if you attempt to disable a service that other enabled services depend on, the call will fail. The API call to disable the service will result in an error message. To disable the specified service and all of the services that depend on it, set the `disable_dependent_services` parameter on the [`services.disable`](/service-usage/docs/reference/rest/v1/services/disable) request to `true`. \n\n### console\n\nTo disable an API for a project:\n\n1. Go to the Google Cloud console [API Dashboard](https://console.cloud.google.com/project/_/apis/dashboard) page. \n [Go to the API Dashboard page](https://console.cloud.google.com/project/_/apis/dashboard)\n2. Select the Google Cloud project where you want to disable\n an API by performing one of the following:\n\n - Click on a Google Cloud project under **Select a recent project**.\n\n - Use the Google Cloud project browser by performing the following\n steps:\n\n 1. Click **Select project** to open the Google Cloud project browser.\n 2. Find your project and then click on the Google Cloud project name.\n 3. Click **Open** to open the project.\n3. Click the API you want to disable. If you need help finding the API, use\n the **Search for APIs \\& Services** box near the top of the page. A page\n describing the API appears.\n\n4. Click *stop* **Disable API**.\n\n### gcloud\n\nRun the following command to disable the Pub/Sub API service for\nyour current project: \n\n```\ngcloud services disable pubsub.googleapis.com\n```\n\nThe command produces output similar to the following: \n\n```\nWaiting for async operation operations/acf.e9d0943b-55d9-4ac0-8af4-745e1b8983f8 to complete...\nOperation finished successfully.\n```\n\nYou can use the following command to get the operation details: \n\n```\ngcloud services operations describe operations/acf.e9d0943b-55d9-4ac0-8af4-745e1b8983f8\n```\n\n### curl\n\nThe following command disables the Pub/Sub API service on\nyour project: \n\n gcurl -d '{}' \"https://serviceusage.googleapis.com/v1/projects/${PROJECT_NUMBER}/services/pubsub.googleapis.com:disable\"\n\nLike `services.enable`, [`services.disable`](/service-usage/docs/reference/rest/v1/services/disable)\nreturns an operation resource, which you can poll by using its `name`."]]
