Google Cloud에서 애플리케이션에 API 관리를 추가한 후 API 관리 기능이 필요하지 않다고 판단되면 Cloud Endpoints Frameworks를 구성하여 API 관리를 중지할 수 있습니다.
API 관리를 삭제해도 API 제공은 중지되지 않습니다. API 제공을 중지하려면 Google Cloud 콘솔의 App Engine 설정 페이지에서 애플리케이션을 중지하거나 Google Cloud 프로젝트를 삭제하면 됩니다. 자세한 내용은 애플리케이션 중지 및 프로젝트 종료를 참고하세요.
앞에서 전송한 요청에 대한 로그 항목이 Produced API 로그에 포함되어 있지 않습니다.
빌드 구성에서 종속 항목 삭제
필요하지 않은 경우에도 빌드 구성에서 종속 항목을 삭제하려고 할 수 있습니다.
빌드 구성에서 종속 항목을 삭제하려면 다음 안내를 따르세요.
pom.xml 파일이나 build.gradle 파일을 백업합니다.
다음 종속 항목을 삭제합니다.
endpoints-management-control-appengine
endpoints-management-control-appengine-all
endpoints-framework-auth
프로젝트를 삭제한 후 API를 빌드합니다.
Maven
mvnclean
mvnpackage
Gradle
gradleclean
gradlebuild
애플리케이션을 다시 배포합니다.
Maven
mvnappengine:deploy
Gradle
gradleappengineDeploy
API를 테스트하여 예상대로 작동하는지 확인합니다.
관리형 서비스 삭제
Endpoints 프레임워크는 Google의 Service Management를 사용하여 API를 관리합니다.
gcloud endpoints services
deploy 명령어를 사용하여 OpenAPI 문서를 배포하면 이 명령어는 Service Management를 사용하여 API에 대한 관리형 서비스를 만듭니다. Endpoints > 서비스 페이지와 로그 뷰어 페이지의 생성된 API 로그에 있는 데이터가 필요하지 않으면 API의 관리형 서비스를 삭제할 수 있습니다. 이렇게 하면 Google Cloud 콘솔에서 데이터가 삭제됩니다.
관리형 서비스를 삭제하려면 다음 단계를 따르세요.
gcloud CLI (gcloud)에 Google Cloud의 데이터 및 서비스에 액세스할 수 있는 권한이 있는지 확인합니다.
gcloudauthlogin
다음을 입력하여 Google Cloud프로젝트의 프로젝트 ID를 표시합니다.
gcloudprojectslist
이전 단계의 해당 프로젝트 ID를 사용하여 기본Google Cloud 프로젝트를 애플리케이션이 있는 프로젝트로 설정합니다.
gcloudconfigsetproject[YOUR_PROJECT_ID]
Google Cloud 프로젝트에 있는 모든 관리형 서비스의 이름을 가져옵니다.
gcloudendpointsserviceslist
Service Management에서 서비스를 삭제합니다. SERVICE_NAME은 삭제할 서비스 이름으로 바꿉니다.
gcloud endpoints services delete SERVICE_NAME
gcloud endpoints services delete를 실행해도 관리형 서비스가 즉시 삭제되지는 않습니다. Service Management에서 30일 동안 관리형 서비스가 사용 중지되므로 필요한 경우 복원할 수 있습니다. 30일 이후에는 Service Management에서 관리형 서비스가 영구적으로 삭제됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-08(UTC)"],[[["\u003cp\u003eYou can disable Cloud Endpoints Frameworks API management features without stopping your API from being served, if it was previously added to your application.\u003c/p\u003e\n"],["\u003cp\u003eTo remove API management, you will need to modify the \u003ccode\u003eweb.xml\u003c/code\u003e and \u003ccode\u003eappengine-web.xml\u003c/code\u003e files within your API project, clean and rebuild the API, then redeploy the application.\u003c/p\u003e\n"],["\u003cp\u003eAfter removing the API Management, you can verify it is no longer being managed by checking the Google Cloud Console's Endpoints Services page and reviewing the request counter and log entries.\u003c/p\u003e\n"],["\u003cp\u003eYou have the option to remove API management dependencies from your build configuration files (\u003ccode\u003epom.xml\u003c/code\u003e or \u003ccode\u003ebuild.gradle\u003c/code\u003e) by deleting specific dependency entries and redeploying.\u003c/p\u003e\n"],["\u003cp\u003eIf you no longer need the data from the Google Cloud Console's \u003cstrong\u003eEndpoints\u003c/strong\u003e > \u003cstrong\u003eServices\u003c/strong\u003e page or the \u003cstrong\u003eProduced API\u003c/strong\u003e log, you can delete the managed service for your API, by using \u003ccode\u003egcloud endpoints services delete\u003c/code\u003e which will initiate a 30-day disabling period before permanent deletion.\u003c/p\u003e\n"]]],[],null,["# Removing API management\n\nIf you added API management to your application on Google Cloud, and\nsubsequently decide that you don't want the API management features, you can configure\nCloud Endpoints Frameworks to stop managing your API.\n\n\u003cbr /\u003e\n\n\nRemoving API management doesn't stop your API from being served. If you want\nto stop serving your API, you can either disable the application on the **App\nEngine Settings** page in the Google Cloud console, or\nyou can delete the Google Cloud project. See [Disabling\nan application and shutting down a project](https://cloud.google.com/appengine/docs/flexible/python/managing-projects-apps-billing#disabling_an_application) for more information.\n\n\u003cbr /\u003e\n\nTo remove API management:\n\n1. Backup your API project's `web.xml` and `appengine-web.xml` files.\n\n2. In your API project's `web.xml` file, remove the following:\n\n - The `endpoints-api-configuration` filter.\n - The `endpoints-api-controller` filter.\n - The `endpoints-api-configuration` filter-mapping.\n - The `endpoints-api-controller` filter-mapping.\n\n After deleting the filters and filter mappings, your `web.xml` should\n be similar to the following: \n\n \u003cweb-app xmlns=\"http://xmlns.jcp.org/xml/ns/javaee\"\n xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n xsi:schemaLocation=\"http://xmlns.jcp.org/xml/ns/javaee\n http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd\"\n version=\"3.1\"\u003e\n \u003c!-- Wrap the backend with Endpoints Frameworks v2. --\u003e\n \u003cservlet\u003e\n \u003cservlet-name\u003eEndpointsServlet\u003c/servlet-name\u003e\n \u003cservlet-class\u003ecom.google.api.server.spi.EndpointsServlet\u003c/servlet-class\u003e\n \u003cinit-param\u003e\n \u003cparam-name\u003eservices\u003c/param-name\u003e\n \u003cparam-value\u003ecom.example.skeleton.MyApi\u003c/param-value\u003e\n \u003c/init-param\u003e\n \u003c/servlet\u003e\n \u003c!-- Route API method requests to the backend. --\u003e\n \u003cservlet-mapping\u003e\n \u003cservlet-name\u003eEndpointsServlet\u003c/servlet-name\u003e\n \u003curl-pattern\u003e/_ah/api/*\u003c/url-pattern\u003e\n \u003c/servlet-mapping\u003e\n \u003c/web-app\u003e\n\n3. In your `appengine-web.xml` file, remove the line that defines the\n `ENDPOINTS_SERVICE_NAME` environment variable. If `ENDPOINTS_SERVICE_NAME`\n is the only environment variable that you have defined, remove the entire\n `env-variables` section.\n\n4. Clean your project and then build your API:\n\n ### Maven\n\n ```bash\n mvn clean\n mvn package\n ```\n\n ### Gradle\n\n ```bash\n gradle clean\n gradle build\n ```\n5. Redeploy your application:\n\n \u003cbr /\u003e\n\n ### Maven\n\n ```java\n mvn appengine:deploy\n ```\n\n ### Gradle\n\n ```java\n gradle appengineDeploy\n ```\n\n \u003cbr /\u003e\n\nAfter you redeploy your application, Cloud Endpoints Frameworks stops managing\nyour API.\n\nVerifying API management removal\n--------------------------------\n\nTo verify that Endpoints Frameworks is no longer managing your API:\n\n1. In the Google Cloud console, go to the **Endpoints** \\\u003e **Services** page.\n\n\n [Go to the Endpoints Services page](https://console.cloud.google.com/endpoints)\n\n \u003cbr /\u003e\n\n2. Write down the number of requests to one of the methods in your API.\n\n3. Click the `View logs` link for the method.\n\n4. In the `Produced API` log, write down the date and time of the most recent\n log entry.\n\n5. Send some requests to the method in your API.\n\n6. In the Google Cloud console, go to the **Endpoints** \\\u003e **Services** page.\n\n\n [Go to the Endpoints Services page](https://console.cloud.google.com/endpoints)\n\n \u003cbr /\u003e\n\n The request counter for the method isn't updated.\n7. Click the `View logs` link for the method.\n\n The `Produced API` log doesn't contain log entries for the requests that\n you sent.\n\nRemoving dependencies in your build configuration\n-------------------------------------------------\n\nAlthough not required, you might want to remove dependencies in your build\nconfiguration.\n\nTo remove dependencies in your build configuration:\n\n1. Backup your `pom.xml` file or your `build.gradle` file.\n\n2. Remove the following dependencies:\n\n - `endpoints-management-control-appengine`\n - `endpoints-management-control-appengine-all`\n - `endpoints-framework-auth`\n3. Clean your project and then build your API:\n\n ### Maven\n\n ```bash\n mvn clean\n mvn package\n ```\n\n ### Gradle\n\n ```bash\n gradle clean\n gradle build\n ```\n4. Redeploy your application:\n\n \u003cbr /\u003e\n\n ### Maven\n\n ```java\n mvn appengine:deploy\n ```\n\n ### Gradle\n\n ```java\n gradle appengineDeploy\n ```\n\n \u003cbr /\u003e\n\n5. Test your API to make sure it is working as expected.\n\nDeleting the managed service\n----------------------------\n\n\nEndpoints Frameworks uses Google's Service Management to manage your API.\nWhen you deployed the OpenAPI document by using the `gcloud endpoints services\ndeploy` command, the command used Service Management to create a\nmanaged service for your API. If you don't need the data on the\n**Endpoints** \\\u003e **Services** page and in the **Produced API** log on the **Logs Viewer**\npage, you can delete the managed service for your API, which removes the data\nfrom the Google Cloud console.\n\n\u003cbr /\u003e\n\nTo delete the managed service:\n\n1. Make sure that the gcloud CLI (`gcloud`) is authorized to access your\n data and services on Google Cloud:\n\n gcloud auth login\n\n2. Enter the following to display the project IDs for your Google Cloud\n projects:\n\n gcloud projects list\n\n3. Using the applicable project ID from the previous step, set the default\n Google Cloud project to the one that your application is in:\n\n gcloud config set project [YOUR_PROJECT_ID]\n\n4. Obtain the name of all managed services in your Google Cloud project:\n\n gcloud endpoints services list\n\n5. Delete the service from Service Management. Replace\n \u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e with the name of the service you want\n to remove.\n\n ```\n gcloud endpoints services delete SERVICE_NAME\n ```\n\n Running `gcloud endpoints services delete` doesn't immediately delete the\n managed service. Service Management disables the managed service for\n 30 days, which allows you time to restore it if you need to. After 30 days,\n Service Management permanently deletes the managed service.\n\nWhat's next\n-----------\n\n- To restore a managed service, see\n [Restoring a managed service](/endpoints/docs/frameworks/java/restore-managed-service).\n\n- For information on the `gcloud` commands used on this page, see the\n [`gcloud` reference](/sdk/gcloud/reference).\n\n- For information on Service Management, see\n [Creating and deleting managed services](/service-infrastructure/docs/create-services)."]]
