Resource Constraints & Pool Constraint Policies
To address the ever-dynamic cloud infrastructure where resources are being created and deleted continuously, DigiUsher introduces a set of tools to help limit the related expenses and the lifetime of individual assets. The following feature is implemented in form of constraints that User can set for a specific resource or generally for a Pool.
There are two constraint types that can be set:
- TTL constraint - time to live, a resource should not live more than the specified period in hours. Input as integer, 1-720 hours.
- Expenses constraint - resource spendings should not exceed the specified amount in dollars. Input as integer, min 1$. When DigiUsher discovers active resources in the connected source, it checks that they don’t violate any existing Pool constraints that were applied as policies before.
When a resource hits a constraint, both manager and owner of the resource are alerted via email and a notification appears on the Task panel in form of a separate task. If a resource is unassigned - alerts are sent to organization managers.
As of now, DigiUsher provides solely notifications about violated constraints and does not interact with the connected source itself to perform any constraint-related adjustments.
Resources Constraints
The Constraints tab can be accessed on the Details page related to a resource. Navigate to the desired asset by selecting the appropriate resource group in the left sidebar and click on its ID.
Select the Constraints tab, click on the pencil image 
next to a constraint’s name and fill in the values for TTL or the Expense limit in the empty fields. Use the slider to enable/disable the current setting.
If a resource doesn’t have a specific constraint set, it inherits the policies from its Pool. However, resource owner or manager can override an existing Pool constraint policy for an individual resource by issuing a custom constraint for any given asset.
Pool Constraint Policies
This is a more high-level setting that facilitates the flow in a way that allows implementing policies for entire Pools instead of a single resource. Thus, a manager can enforce all resources in the Pool to share constraints so that they are applied to all resources in this Pool, while custom resource-specific constraints can still exist and yet override the general policy.
Click on Pools in the left sidebar and choose a Pool group or its sub Pool.
Click on the pencil image next to a constraint’s name and fill in the values for TTL or the Expense limit in the empty fields. Use the slider to enable/disable the current setting.
A constraint will not be visible if the related resource has already been deleted from DigiUsher or if a resource has been tracked only by imported billing data.
Pool Deletion
he Pool structure can be changed by deleting unnecessary Pools via the dedicated section of the main page. This option is not available for Pools that have sub-Pools - latter have to be deleted first.
An employee should have the Manager role in the parent of the Pool that they want to delete.
To delete a Pool, click on its name in the Pool section and then on the pencil image to bring up the “Edit” menu.
When a Pool is deleted:
- all resources are reassigned to its parent Pool;
- all rules that used to point to this Pool are redirected to its root.