앞서 설명한 사용 사례를 지원하는 것 외에도 확장 프로그램 프로세서는 다음과 같은 내장 Apigee 기능의 모든 이점을 제공합니다.
보안: 지능화된 API 보안은 API 트래픽을 지속적으로 모니터링하고 분석하여 의심스러운 API 요청을 식별하고 이러한 요청을 차단하거나 플래그를 지정하는 도구를 제공합니다.
수익 창출: Apigee 내에서 만든 맞춤 API 제품에 요금제를 추가하여 API가 사용될 때마다 수익을 창출합니다.
추적 가능성: Apigee의 분산 추적 시스템을 사용하면 여러 애플리케이션, 서비스, 데이터베이스, 프록시 간에 분산된 시스템에서 요청을 추적할 수 있습니다.
비즈니스 인텔리전스: Apigee API Analytics는 부하 분산기를 통해 흐르는 풍부한 정보를 수집하여 UI에서 데이터 시각화를 제공하거나 오프라인 분석을 위해 데이터를 다운로드하는 기능을 제공합니다.
Apigee 확장 프로그램 프로세서 작동 방식
Apigee 확장 프로그램 프로세서는 애플리케이션 부하 분산기의 데이터 처리 경로에서 Cloud Load Balancing을 사용하여 Apigee에 콜아웃을 보낼 수 있는 트래픽 확장 프로그램(서비스 확장 프로그램의 한 유형)입니다. 애플리케이션 부하 분산기와 서비스 확장 프로그램이 구성되면 다음 그림과 같이 애플리케이션 부하 분산기를 통과하는 트래픽이 서비스 확장 프로그램을 사용하여 Apigee 프록시 호출을 트리거합니다.
그림 1: Apigee 확장 프로그램 프로세서의 인프라와 Dataflow
이 다이어그램은 Apigee 확장 프로그램 프로세서 구성의 필수 구성요소를 간략히 보여줍니다.
모든 애플리케이션 백엔드를 포함하는 네트워크 엔드포인트 그룹(NEG)으로 구성된 백엔드 서비스가 있는 애플리케이션 부하 분산기
확장 프로그램 프로세서 전용 환경이 있고 apigee-service-extension-enabled 속성이 true로 설정된 Apigee 인스턴스
Private Service Connect (PSC) 엔드포인트를 사용하여 Apigee 런타임 평면에 연결하도록 구성된 트래픽 확장 프로그램(서비스 확장 프로그램의 한 유형)
확장 프로그램 프로세서를 사용하는 경우 환경, 환경 그룹, API 프록시에 추가 한도가 적용됩니다.
확장 프로그램 프로세서 구성에 사용되는 환경 그룹에는 최대 하나의 환경을 연결할 수 있습니다.
확장 프로그램 프로세서를 구성할 때 사용되는 환경에는 최대 50개의 API 프록시를 배포할 수 있습니다.
확장 프로그램 프로세서의 전용 환경에 배포된 API 프록시는 모두 동일한 프록시 유형이어야 합니다. API 프록시는 모두 표준 API 프록시이거나 모두 확장 가능 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-08-19(UTC)"],[],[],null,["# Apigee Extension Processor overview\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nThe Apigee Extension Processor lets Apigee customers add API management capabilities to Google Cloud products and services, or external services, exposed using Cloud Load Balancing.\n\n\u003cbr /\u003e\n\nTo get started using the Apigee Extension Processor, see the [Apigee Extension Processor quickstart](/apigee/docs/api-platform/service-extensions/extension-processor-quickstart).\n\nUse cases for the Apigee Extension Processor\n--------------------------------------------\n\nApigee customers using the Extension Processor can select from a range of Apigee policies that\napply API management capabilities to any products or services exposed using a Google Cloud load balancer.\n\nWith the Extension Processor, you can:\n\n- **Secure access to Google Cloud workloads.**\n\n Choose from a wide range of Apigee policies to apply to your load balancer traffic, including [VerifyApiKey](/apigee/docs/api-platform/reference/policies/verify-api-key-policy),\n [OAuthV2](/apigee/docs/api-platform/reference/policies/oauthv2-policy),\n and [VerifyJWS](/apigee/docs/api-platform/reference/policies/verify-jws-policy).\n- **Apply quota enforcement to network traffic.**\n\n This capability lets API providers enforce limits on the number of API calls made to backend services over a\n specified time period. For example, you can use the [Quota](/apigee/docs/api-platform/reference/policies/quota-policy) policy to limit calls to 1 request per minute, or to 10,000 requests per month.\n- **Manage Google token injection for authenticating requests.**\n\n Using the Extension Processor and the [AssignMessage](/apigee/docs/api-platform/reference/policies/assign-message-policy) policy,\n you can inject a [Google access token](/docs/authentication/token-types#access) or [Google ID token](/docs/authentication/token-types#id)\n into client request headers to manage access to GOogle-authenticated backend services and products.\n- **Support native protocols.**\n\n The Extension Processor unlocks support for native protocols such as [gRPC bi-directional streaming](https://grpc.io/docs/what-is-grpc/core-concepts/#service-definition),\n [server-sent events (SSE)](/apigee/docs/api-platform/develop/server-sent-events), and [HTTP/3](/load-balancing/docs/https#QUIC).\n\nBenefits\n--------\n\nIn addition to supporting the use cases described earlier, the Extension Processor provides all the benefits of built-in Apigee features, such as:\n\n- **Security**: Advanced API Security continually monitors and analyzes your API traffic to identify suspicious API requests and provides tools to block or flag those requests.\n- **Monetization**: Generate revenue whenever your APIs are used by adding rate plans to customized API products you create within Apigee.\n- **Traceability**: Apigee's distributed tracing system lets you track requests in distributed systems across multiple applications, services, and databases, and proxies.\n- **Business intelligence**: Apigee API Analytics collects the wealth of information flowing through your load balancer, providing data visualization in the UI or the ability to download data for offline analysis.\n\nHow Apigee Extension Processor works\n------------------------------------\n\nThe Apigee Extension Processor is a traffic extension (a type of [service extension](/service-extensions/docs/lb-extensions-overview)) that lets you use Cloud Load Balancing\nto send callouts to Apigee from the data processing path of the application load balancer. Once the application load balancer\nand service extension are configured, traffic flowing through the application load balancer will trigger calls to\nApigee proxies using the service extension, as shown in the following figure:\n\n**Figure 1**: Infrastructure and dataflow for the Apigee Extension Processor.\n\nThe diagram outlines the required components of the Apigee Extension Processor configuration:\n\n- An Application Load Balancer with a backend service configured with a Network Endpoint Group (NEG) covering all application backends.\n- An Apigee instance with a dedicated environment for the Extension Processor and the property `apigee-service-extension-enabled` set to `true`.\n- A [traffic extension](/service-extensions/docs/configure-traffic-extensions) (a type of service extension) configured to use a Private Service Connect (PSC) endpoint to connect to the Apigee runtime plane.\n- A [no-target Apigee API proxy](/apigee/docs/api-platform/fundamentals/build-simple-api-proxy) running in a special environment. The proxy is used to apply API management capabilities to the load balancer traffic.\n\n\u003cbr /\u003e\n\nAs shown in the flow diagram:\n\n- **1**: The client sends a request to the Application Load Balancer.\n- **2**: The Application Load Balancer reviews the traffic and calls out to the Service Extension.\n- **3**: The Service Extension implementation in the Apigee message processor applies any relevant API management policies and returns the request, with any modifications, to the Application Load Balancer.\n- **4**: The Application Load Balancer completes processing and forwards the request to the backend service. Similar processing occurs for the response path from the backend service to the Application Load Balancer and to the client.\n\nFor more information, see [Cloud Load Balancing extensions](/service-extensions/docs/overview#integration-lb-callouts).\n\nLimitations\n-----------\n\nThe Apigee Extension Processor has the following known limitations:\n\n- The Extension Processor is applied at the load balancer level. All traffic passing through the load balancer is processed by the same proxy, with no base path or URL distinction.\n- Traffic through the Extension Processor is subject to the same quotas as the Cloud Load Balancing. Relevant limits and quotas include the following:\n\n - Maximum number of traffic extensions per load balancer: 1\n - Maximum traffic extensions per project: 100\n - Maximum extension chains per project: 5\n - Maximum extensions per resource: 3\n\n For more information, see [Quotas and limits](/load-balancing/docs/quotas).\n- Additional limits apply to environments, environment groups, and API proxies when using the Extension Processor:\n - A maximum of **one** environment can be attached to the environment group used to configure the Extension Processor.\n - The environment used when configuring the Extension Processor can have a maximum of **50** API proxies deployed.\n - The API proxies deployed in the dedicated environment for the Extension Processor must all be of the same [*proxy type*](/apigee/docs/api-platform/fundamentals/understanding-apis-and-api-proxies#proxy-types). The API proxies must be either all **standard** API proxies or all **extensible** API proxies. Standard and extensible API proxies can't be mixed in the Extension Processor environment.\n\n For more information, see [Create an Apigee environment](/apigee/docs/api-platform/service-extensions/extension-processor-quickstart#create-apigee-environment).\n\n For more information on Apigee limits generally, see [Limits](/apigee/docs/api-platform/reference/limits).\n- The following Apigee policies are not supported for use with the Extension Processor:\n - [Publish message](/apigee/docs/api-platform/reference/policies/publish-message-policy)\n - [ExternalCallout](/apigee/docs/api-platform/reference/policies/external-callout-policy)\n - [IntegrationCallout](/apigee/docs/api-platform/reference/policies/integration-callout-policy)\n - [ServiceCallout](/apigee/docs/api-platform/reference/policies/service-callout-policy)\n - [SetIntegrationRequest](/apigee/docs/api-platform/reference/policies/set-integration-request-policy)\n - [MessageLogging](/apigee/docs/api-platform/reference/policies/message-logging-policy)\n - [GenerateJWT](/apigee/docs/api-platform/reference/policies/generate-jwt-policy)\n\nPricing\n-------\n\nIn addition to costs associated with your Apigee Subscription or Pay-as-you-go pricing plans,\nthe following networking costs may apply when using Apigee Extension Processor:\n\n- [Service Extensions pricing](/service-extensions/pricing)\n- [Backend service pricing](https://cloud.google.com/vpc/network-pricing#lb)\n- [Private Service Connect charges](https://cloud.google.com/vpc/network-pricing#psc-consumer-data-processing)\n\nWhat's next\n-----------\n\n- Learn how to [Get started with the Apigee Extension Processor](/apigee/docs/api-platform/service-extensions/extension-processor-quickstart).\n- Learn more about working with [Service Extensions](/service-extensions/docs/overview).\n- Explore how Apigee Extension Processor works with the [Apigee APIM Operator for Kubernetes](/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-overview)."]]
