Apigee 정책은 코드를 작성하거나 백엔드 서비스를 수정하지 않고도 API를 보완하여 트래픽을 제어하고 성능을 향상시키고 보안을 강화하며 API의 유용성을 향상시킵니다.
또한 Apigee는 자바스크립트, Python, 자바, XSLT 스타일시트 형식으로 맞춤 로직을 구현할 수 있는 확장 정책을 제공합니다.
정책 카테고리 및 유형
정책의 카테고리는 정책의 기능 영역(예: 보안 또는 미디에이션)을 나타냅니다.
정책은 아래 카테고리별로 정렬되어 표시됩니다.
정책 유형은 Apigee에서 정책을 사용할 수 있는 방법을 나타냅니다.
표준 정책은 내부 개발 및 경량형 API 솔루션에 적합합니다.
표준 정책은 모든 환경 유형에서 사용할 수 있습니다.
표준 정책 목록을 보려면 카테고리별 표준 정책을 참조하세요.
확장 가능한 정책은 트래픽 관리, 중재, 보안에 대한 정책을 포함하여 표준 정책보다 더 많은 기능을 제공합니다. 확장 가능한 정책에는 자바스크립트, Python, 자바, XSLT 스타일시트 형식으로 커스텀 로직을 구현하는 정책도 포함되어 있습니다.
확장 가능한 정책은 중간 및 포괄적인 환경 유형에서만 사용할 수 있습니다. 확장 가능한 정책을 사용하면 프록시가 확장 가능한 프록시로 자동 변환되며, 이는 비용 및 기타 영향을 미칠 수 있습니다. 자세한 내용은 사용한 만큼만 지불 사용 권한 및 구독 2024를 참조하세요.
[[["이해하기 쉬움","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-18(UTC)"],[[["\u003cp\u003eApigee policies enhance APIs by managing traffic, boosting performance, strengthening security, and expanding API functionality without the need for custom coding or modifying backend services.\u003c/p\u003e\n"],["\u003cp\u003eApigee offers both standard and extensible policies; standard policies are for lightweight API solutions and internal development, while extensible policies provide greater functionality for traffic management, mediation, security and custom logic, but require intermediate or comprehensive environment types.\u003c/p\u003e\n"],["\u003cp\u003eStandard policies are categorized into traffic management, mediation, security, and extension, with examples like SpikeArrest for traffic and AccessControl for security.\u003c/p\u003e\n"],["\u003cp\u003eExtensible policies also fall into traffic management, mediation, security, and extension, offering advanced features such as caching and threat protection, and they allow custom logic with JavaScript, Python, Java, and XSLT.\u003c/p\u003e\n"],["\u003cp\u003eThe choice between standard and extensible policies depends on the required functionality and the environment type deployed, with standard policies being preferred if both types can fulfill the necessary functions.\u003c/p\u003e\n"]]],[],null,["# Policy reference 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\nApigee's policies augment your APIs to control\ntraffic, enhance performance, enforce security, and increase the utility of your APIs, without\nrequiring you to write code or modify backend services.\n\nIn addition, Apigee provides extension policies that let you implement custom logic in the\nform of JavaScript, Python, Java, and XSLT stylesheets.\n\nPolicy categories and types\n---------------------------\n\nA policy's *category* indicates the functional area (for example, security or mediation) for the policy.\nPolicies are shown sorted by category below.\n\nThe policy type refers to how the policy can be used in Apigee:\n\n- **Standard policies** are suitable for internal development and lightweight API solutions. Standard policies can be used with any [environment type](/apigee/docs/api-platform/fundamentals/environments-overview#environment-types). To see the list of standard policies, see [Standard policies by category](#standard-policy-categories).\n- **Extensible policies** provide more functionality than standard policies, including for traffic management, mediation, and security. The extensible policies also include policies to implement custom logic in the form of JavaScript, Python, Java, and XSLT stylesheets. \n\n Extensible policies can be used with intermediate and comprehensive environment types only. Using an extensible policy automatically converts that proxy to an [Extensible proxy](/apigee/docs/api-platform/fundamentals/understanding-apis-and-api-proxies#proxy-types), which could have cost and other implications. Check the [Pay-as-you-go entitlements](/apigee/docs/api-platform/reference/pay-as-you-go-updated-entitlements) and [Subscription 2024](/apigee/docs/api-platform/reference/subscription-entitlements#subscription-2024-entitlements) for information. \n\n To see the list of extensible policies, see [Extensible policies by category](#standard-policy-categories).\n\nFor [Pay-as-you-go](/apigee/docs/api-platform/reference/pay-as-you-go-updated-overview) users, the types of policies you can use in a proxy depend on the\n[environment types](/apigee/docs/api-platform/reference/pay-as-you-go-environment-types)\nyou plan to deploy that proxy to. See [Pay-as-you-go](/apigee/docs/api-platform/reference/pay-as-you-go-updated-overview) for more information.\n\nIf there are two policies, one standard and one extensible, that would both perform the functions\nyou need, use the standard policy.\n\nStandard policies by category\n-----------------------------\n\nFollowing are the categories for the standard policies:\n\nExtensible policies by category\n-------------------------------\n\nFollowing are the extensible policies, by category. Proxies with extensible policies can only be\ndeployed to intermediate and comprehensive environments. Extensible policies are indicated in the user\ninterface with this icon:\n."]]
아이콘으로 표시됩니다.