Skip to content

Manually Marked Use Case

For resources to qualify as Manually Marked, it needs to be tagged. Unless configured otherwise tag key is bkbcloud-ManuallyMarked, value can be anything.

[!NOTE] Manually Marked resources will not be evaluated by other use cases and estimate saving is always 0.

Why use this use case?

  1. When resource is not captured by other use cases, but you know that it is f.e. Unused
  2. You want to remove the resource from being identified f.e. resource is identified as Over-Provisioned, but you know that there is nothing to be done with it or it’s a false-positive
  3. You want to track price changes (even deletion) on the resource, because you plan to perform some cost saving activity

Actions to take against identified resources

This is a special use case, where no action is expected.

Same as for other use-cases, if a price of a resource changes, it will be tracked and counted towards the savings, even if the resource is deleted, total saving will be tracked.

False positives

Because of nature manually tagging the resource upfront, we consider this use case as not having any false positives.