버튼 클릭 한 번으로 API 허브에서 직접 Apigee 및 Apigee Hybrid 런타임 프로젝트에 있는 배포된 프록시를 등록할 수 있습니다.
그림 1. Apigee 및 Apigee Hybrid에서 API 자동 등록
프록시가 API 허브에 API 리소스로 등록됩니다. 프록시를 등록하려면 런타임 프로젝트를 API 허브에 연결해야 합니다. 프로젝트를 연결할 때 API 허브는 각 프록시 정의에 대해 다음 정보를 등록합니다.
이름
버전
환경 및 배포 세부정보
Apigee 인스턴스 유형(Apigee X 또는 Apigee Hybrid)
API 허브는 6시간마다 한 번씩 주기적으로 Apigee 프로젝트에 연결하는 스케줄러를 실행하고 최신 프록시 정의를 가져옵니다. 새로 연결된 프로젝트의 경우 스케줄러가 모든 프록시 정의를 가져온 후 API 허브에 등록합니다.
기존 프로젝트의 경우 스케줄러가 프록시 정의에 대한 변경사항만 가져온 후 그에 따라 API 허브에서 프록시 정보를 업데이트합니다.
런타임 프로젝트 연결
Apigee 런타임 프로젝트를 API 허브에 연결하려면 다음 단계를 따르세요.
Google Cloud 콘솔에서 API 허브 > 설정 > 프로젝트 연결 페이지로 이동합니다.
런타임 프로젝트 연결을 클릭합니다. 그러면 리소스 선택 창이 표시됩니다.
Apigee가 설치된 Google Cloud 프로젝트를 클릭합니다. 오류가 없으면 프로젝트가 API 허브에 연결되고 프로젝트 연결 페이지에 나열됩니다. 그러나 실제 프록시 등록 프로세스는 스케줄러가 다음 번 실행된 후에 시작됩니다.
런타임 프로젝트 분리
런타임 프로젝트를 분리하면 API 허브에서 해당 프로젝트에 등록된 모든 API를 삭제합니다.
API 허브에서 Apigee 런타임 프로젝트를 분리하려면 다음 단계를 수행합니다.
Google Cloud 콘솔에서 API 허브 > 설정 > 프로젝트 연결 페이지로 이동합니다.
분리하려는 프로젝트에서 프로젝트 분리를 클릭합니다.
고려사항
API를 자동 등록하려고 할 때는 다음을 고려하세요.
Apigee에서 가져온 모든 엔드포인트에는 기본적으로 https:// 프리픽스가 지정됩니다.
어떤 환경에도 배포되지 않은 프록시는 프로젝트에서 가져오지 않습니다.
환경에 배포된 프록시만 가져옵니다. 환경은 환경 그룹의 일부여야 합니다.
API 허브에서 VPC 서비스 제어를 지원하지 않습니다. 따라서 Apigee 런타임 프로젝트에 VPC 서비스 제어를 사용 설정한 경우 API 허브에서 프로젝트에 액세스할 수 없습니다.
런타임 프로젝트에 Apigee API가 사용 설정되지 않은 경우 API 허브에서 프로젝트에 액세스할 수 없습니다.
[[["이해하기 쉬움","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-04(UTC)"],[[["\u003cp\u003eAPI proxies from Apigee and Apigee hybrid can be automatically registered in API hub by attaching the respective runtime project.\u003c/p\u003e\n"],["\u003cp\u003eAPI hub's scheduler periodically retrieves and registers new or updated proxy definitions from attached Apigee projects, running once every six hours.\u003c/p\u003e\n"],["\u003cp\u003eAttaching a runtime project to API hub requires selecting the Google Cloud project where Apigee is installed in the "Project associations" page.\u003c/p\u003e\n"],["\u003cp\u003eDetaching a runtime project from API hub removes all registered APIs associated with that project, though created attributes are retained.\u003c/p\u003e\n"],["\u003cp\u003eOnly proxies deployed in environments that are part of an environment group are fetched, and VPC Service Controls is not supported by API hub.\u003c/p\u003e\n"]]],[],null,["# Auto-register Apigee proxies\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\nThis page describes how to automatically register Apigee proxies in API hub. API hub lets you to register deployed proxies from both Apigee and Apigee hybrid runtime projects directly into API hub. This auto-registration process enables API hub to register API resources from multiple API gateways.\n\nHow auto-registration works\n---------------------------\n\n\nWhen you attach an Apigee runtime project to API hub, information such as the proxy's name, environment and deployment details, and the type of Apigee instance (Apigee or Apigee hybrid) is automatically registered.\n**Figure 1.** Auto-register APIs from Apigee and Apigee hybrid.\n\n### Project associations and plugins\n\n| **Deprecated:** [Pull-based](/apigee/docs/apihub/plugins#plugin-data-ingestion-methods) ingestion is no longer supported for Apigee and Apigee hybrid plugins as of **July 31, 2025** . For existing projects that have pull-based Apigee and hybrid plugins configured, these plugins will continue to function and will be automatically migrated to the push-based type starting **August, 2025**.\n\nWhen you provision API hub as part of Apigee provisioning, it automatically identifies and attaches any associated Apigee runtime projects. This automatically creates an Apigee and hybrid plugin instance by default in API hub and ingests any deployed API proxies from Apigee.\n| **Note:**If you provision API hub directly from the API hub UI, API hub doesn't automatically create a default plugin instance, nor does it auto-register proxies.\n\n\nIf you manually attach any additional Apigee runtime projects (Apigee or Apigee hybrid), API hub offers an option to import additonal API metadata. When this option is selected, API hub automatically creates the necessary plugin instance to manage the metadata import. These plugin instances are key to managing the connection and data ingestion for the auto-registration process.\n\n### Project associations scheduler\n\n| **Note:** This functionality applies only to [pull-based](/apigee/docs/apihub/plugins#plugin-data-ingestion-methods) Apigee and hybrid plugin instances. For push-based plugins, data ingestion is automatically triggered by changes in the source.\n\nAPI hub periodically (once in six hours) runs a scheduler that connects to your\nApigee project, and gets the latest proxy definitions. For the projects that are newly\nattached, the scheduler gets all the proxy definitions, and then registers them in API hub.\nAnd for the existing projects, the scheduler gets only the changes made to the proxy\ndefinitions, and then accordingly updates the proxy information in API hub.\n\nAttach a runtime project\n------------------------\n\n### Before you begin\n\n- If you are attaching an Apigee runtime project, ensure that your Apigee organization doesn't have [Data Residency (DRZ) enabled](/apigee/docs/api-platform/get-started/drz-concepts). API hub doesn't support creating a plugin instance if Data Residency is enabled for your Apigee organization.\n- Grant the [Cloud API hub Runtime Project Attachment Editor (`roles/apihub.runTimeProjectAttachmentsEditor`)](/iam/docs/roles-permissions/apihub#apihub.runTimeProjectAttachmentsEditor) IAM role to your principal account.\n\nTo attach an runtime project to API hub, do the following steps:\n\n1. In the Google Cloud console, go to the **API hub** page.\n\n [Go to API hub](https://console.cloud.google.com/apigee/api-hub)\n2. Click settings **Settings** from the left navigation menu to open the **Settings** page.\n3. Go to the **Project associations** tab and click **Attach runtime project** . This displays the **Select a resource** pane.\n4. Click the Google Cloud project where your runtime project is provisioned.\n5. In the **Project association settings** pane, select the **API assets to automatically import** checkbox. **Note:** API hub automatically creates a plugin instance for the associated runtime project if you choose to import assets. This plugin instance is displayed in the **Associated plugins** column on the **Project associations** page.\n6. Click **Attach**.\n\nEdit project association settings\n---------------------------------\n\nYou can edit the project association settings to change the API assets which are automatically imported. To edit the project association settings, do the following steps:\n\n1. In the Google Cloud console, go to the **API hub** page.\n\n [Go to API hub](https://console.cloud.google.com/apigee/api-hub)\n2. Click settings **Settings** from the left navigation menu to open the **Settings** page.\n3. Go to the **Project associations** tab to view the list of attached projects.\n4. Click **Edit settings** for the desired project.\n5. In the **Project association settings** pane, edit the **API assets to automatically import** checkbox selection.\n6. Click **Save** to apply your changes.\n\nDetach a runtime project\n------------------------\n\n| **Warning:**Detaching a runtime project from API hub also deletes all the associated plugin instances and registered APIs from API hub.\n\nTo detach a runtime project from API hub, do the following steps:\n\n1. In the Google Cloud console, go to the **API hub** page.\n\n [Go to API hub](https://console.cloud.google.com/apigee/api-hub)\n2. Click settings **Settings** from the left navigation menu to open the **Settings** page.\n3. Go to the **Project associations** tab to view the list of attached projects.\n4. Click **Detach project** for the project you want to detach.\n\n| **Note:**Even though all the APIs of the detached project are removed from API hub, the attributes that were created for those APIs aren't deleted, and will still show up in API hub.\n\nConsiderations\n--------------\n\nConsider the following when attempting to attach Apigee runtime projects:\n\n- All endpoints imported from Apigee will be given an `https://` prefix by default.\n- Proxies that aren't deployed in any environment, aren't fetched from the project.\n- Only proxies that are deployed in an environment are fetched. And the environment must be a part of an environment group.\n- Additional attributes representing the Apigee instance type (`Apigee X and Hybrid Environment` and `Apigee X and Hybrid Organization`) are automatically created and added to any proxy API deployments that are imported. **Deprecated:** The Apigee instance type attribute is no longer added to API deployments as of **July 31, 2025** . For existing projects that have Apigee instance type attributes configured, we recommend that you remove these attributes from any filtered search queries. You can use the **Source project** and **Source environment** fields instead.\n- API hub doesn't support [VPC Service Controls](/vpc-service-controls/docs/overview). Hence, if you have enabled VPC Service Control for your Apigee runtime project, API hub can't access the project.\n- If the Apigee API isn't enabled for a runtime project, API hub can't auto-register or import the API proxies.\n\n### Limitations\n\n- API hub doesn't support creating a plugin instance if [Data Residency (DRZ) is enabled](/apigee/docs/api-platform/get-started/drz-concepts) for your Apigee organization.\n\nWhat's next\n-----------\n\n- Learn more about [plugins and plugin instances](/apigee/docs/apihub/plugins).\n- Learn about [curations](/apigee/docs/apihub/curations)."]]
