> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/platform-administration/governance/policies/limit-of-replicas-policy.md). # Limit of Replicas policy Learn more about the Limit of Replicas policy on the Digibee Integration Platform. {% hint style="warning" %} This documentation is **exclusive** to customers using the Consumption-Based Model and may not be applicable to your realm. {% endhint %} Excessive replica settings can lead to significant and unexpected financial costs. Additionally, unnecessary processing in test environments, like keeping an always-on pipeline active or running a large number of replicas without executions, can result in inefficient credit usage and increased costs, especially for consumption-based models.\ \ With the **Limit of Replicas policy**, you can limit: * The minimum number of replicas for each environment. * The maximum number of replicas for each environment. * The target of replicas for each environment (when Autoscalling is off). This will help you to prevent your consumption from misusage and control your credit consumption efficiently. ## How to define the replicas limit To define the number of replicas for each of your environments, follow the steps below: 1. Access the Digibee Integration Platform and click **Administration** at the top right corner. 2. Click **Policies** at the menu on the left side of the page. 3. Click **Deployments** on the top menu. 4. At the **Limit of Replicas row,** click the **Edit icon**. 5. Set the number of replicas for each environment. 6. Click **Save** to implement the changes or **Cancel** to return to the previous screen. Once your Limits of Replicas policy is configured, each new pipeline deployment operation must follow the rules according to your definitions. If a developer forgets to apply your policy, they will be reminded during the deployment phase. In other words, it isn't possible to deploy the pipeline, until the issues are resolved. ## The impact of the Limit of Replicas policy on Platform usage Users responsible for deployments will have their actions constrained by the number of replicas specified in the policy configuration. The following actions can only be performed within the defined limits: * Create deploy * Redeploy * Promote to * Restore * Rollback Users responsible for deployments using [Digibeectl](/documentation/platform-administration/administration/digibeectl.md) are also impacted by the policy. The following actions can only be performed in Digibeectl within the defined limits: * `--create deployment` * `--create redeploy` * `--set deployment rollback` This ensures compliance with the policy while optimizing resource utilization. ## Permissions Users with the **POLICY:UPDATE** permission can modify this policy, while users with the **POLICY:READ** permission can only view it. Viewing this tab also requires the **LICENSE:READ** permission, because the tab's visibility depends on the realm's license model. This permission is required specifically for realms on the Consumption-Based Model. Learn more about permissions in [Access control](/documentation/platform-administration/administration/new-access-control.md). ## Exceptions to the policy The **POLICY:UPDATE** permission allows a user to specify a list of users and groups that are exceptions to the Limit of Replicas policy, allowing them to operate without the established replica limits. To create an exception list, access the **Limit of Replicas policy** on the Digibee Integration Platform and navigate to the **Policy exceptions by environment** section. ### Exceptions for users Type a name or email to add any users who should be considered exceptions within the Limit of Replicas policy. ### Exceptions for groups Click + to add user groups that should be considered exceptions within the Limit of Replicas policy. You can [create a new group](/documentation/platform-administration/administration/new-access-control/access-control-groups.md) if you consider it necessary. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digibee.com/documentation/platform-administration/governance/policies/limit-of-replicas-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.