More control over your FinOps workflow: What’s new in Stable this August

 |  Eric Pinet

Cost recommendations are most useful when your team can quickly distinguish between what requires action, what can wait and what simply does not apply to your organization.

Stable’s August updates give you greater control over that process. You can now formally exclude recommendations while preserving the reasoning behind each decision, choose when to receive commitment expiry reminders and use AWS tags directly in the Resource Explorer.

Here is what’s new.

Keep your recommendations focused with Ignore Rules

Not every cost recommendation is actionable today. Some resources may be part of a migration, support a seasonal workload or fall under an upcoming contract renewal. Other recommendation categories may not apply to your organization at all.

Ignore Rules let you exclude these resources from your active cost recommendations view, helping your team focus on the savings opportunities that are currently relevant.

You can create three types of rules:

  • Tags: Match resources using AWS tags such as env: prod or Team: research. Tag-based rules can also be limited to specific AWS accounts.
  • Resources: Exclude specific resource IDs when you already know exactly which resources should be removed from the active view.
  • Recommendations: Ignore an entire recommendation category across all resources when that type of recommendation is not relevant to your organization.

Rules can be permanent or temporary. By adding an optional “Until” date, you can have a rule expire automatically once a migration, seasonal period or other temporary situation has ended. The affected resources will then return to “Affected” status.

Each rule also includes a reason field, creating a clear record of why the resources were excluded. This gives everyone on your team the context they need, even if they were not involved in the original decision.

Before saving a rule, a live preview shows the number of resources it will affect and the associated potential yearly savings. Once the rule is active, the stats view lets you see what it is excluding and how much potential savings has been set aside.

Ignored resources never disappear from Stable. They remain available under the dedicated “Ignored” tab, with a direct link to the rule covering them, and continue to appear normally in the Resource Explorer.

Read the full Ignore Rules documentation

Choose when to receive commitment expiry reminders

Expiring Savings Plans and Reserved Instances can affect both your coverage and your AWS costs. Stable now lets each user choose how far in advance they want to be notified.

Available reminder intervals include:

  • 30 days before expiry
  • 7 days before expiry
  • 1 day before expiry

Reminder preferences are configured individually. FinOps leads, engineers and other stakeholders can therefore select the schedule that best reflects their responsibilities and planning needs.

Explore your AWS inventory by tag

AWS tags provide valuable context about the teams, applications, environments and workloads behind your cloud resources. Stable now brings that context directly into the Resource Explorer.

A dedicated Tags column displays tags in the resource table, eliminating the need to open each resource individually. When you do need the complete picture, a new Tags tab within the resource details view shows the resource’s full set of tags.

You can also filter the resource table by tag key or value. This makes it easier to isolate a specific environment, application, workload or team and investigate its resources together.

More signals. Better efficiency

These updates give your team more control over how recommendations are reviewed, documented and prioritized. You can remove irrelevant items from the active workflow without losing visibility, prepare for commitment expiries according to your own schedule and use AWS tags to navigate your inventory more efficiently.

Log in to Stable to explore the new features.