New in Stable: Microsoft SSO, advanced filters and 14 new AWS cost recommendations
Stable continues to evolve with new features designed to help teams find AWS savings faster, work more efficiently and bring more people into their FinOps process.
Over the past two releases, we introduced Microsoft Single Sign-On, Advanced Filters across Stable’s main tables and 14 new cost recommendations covering Aurora, DynamoDB, OpenSearch, EBS, CloudTrail, CloudFront, Transfer Family and WAF.
Together, these updates make Stable easier to adopt across enterprise teams and more powerful for identifying cloud waste that is often difficult to spot manually.
Sign in with Microsoft
Stable now supports Single Sign-On through Microsoft, making it easier for Business and Enterprise teams to access the platform using their existing identity provider.
Users can now sign in to Stable with their Microsoft account, without needing a separate Stable-specific password. For organizations already using Microsoft Entra ID, formerly Azure Active Directory, this simplifies access management and keeps authentication aligned with existing internal policies.
That means your team can manage Stable access from the same place it manages other Microsoft identities. When a new teammate is added to your Microsoft tenant, they can be ready to access Stable without additional password setup.
Stable sessions also inherit your organization’s Microsoft security policies, including MFA requirements, conditional access rules and session timeout settings. No additional configuration is required inside Stable.
Existing users can link their Stable account to their Microsoft identity directly from their profile settings. To enable Microsoft SSO for your organization, visit your workspace settings or contact the Stable team.
Advanced Filters across Stable’s main tables
June also brings one of the most requested improvements from Stable users: Advanced Filters.
Every main table in Stable now supports advanced filtering, including Cost Optimisation, Cost Optimisation Resources, Commitment and Resources. Instead of scrolling through long lists of recommendations or resources, teams can create precise views based on what matters most to them.
Filters can be applied to any column in a table, including numeric values, text fields, categories, dates, booleans and tags. For example, a FinOps lead can quickly build a view for easy wins above a specific annual savings threshold, all EC2-related recommendations in a given region or resources tied to a specific owner or environment.
Tag-based filtering is now a first-class option. Teams can filter resources that carry a specific tag, or use the dedicated No Tag filter to surface resources that fall outside tagging policies. This makes it easier to identify gaps in governance, ownership and cost allocation.
Stable also makes recurring workflows easier to manage. Owners and Managers can save named filter presets and share them across the organization. A FinOps lead can create a standard view once, then make it available to the broader team without asking everyone to rebuild the same filters manually.
Active filter sets are also reflected in the page URL. Copy the link, send it to a colleague and they will see the same filtered view instantly.
Each table manages its own saved presets independently, so a preset created for Cost Optimisation stays in that table and does not appear in Commitment or Resources.
14 new AWS cost recommendations
Stable’s recommendation engine now includes 14 additional checks across several AWS services. Each recommendation targets a common cost pattern: a resource, configuration or commitment model that may have made sense at one point, but no longer matches how the workload actually runs.
These new recommendations help teams uncover savings opportunities that are easy to miss in day-to-day AWS operations.
Aurora recommendations
Stable now flags predictable Aurora Serverless workloads that may be better suited to provisioned instances. When an Aurora Serverless database shows a stable and predictable ACU range, switching to a provisioned instance, ideally covered by a Reserved Instance, can reduce costs.
Stable also identifies Aurora clusters where I/O charges represent a significant portion of total storage and I/O spend. In these cases, moving from Aurora Standard storage to Aurora I/O-Optimized storage may lower the total bill by removing per-request I/O charges.
DynamoDB recommendations
Stable now detects unused DynamoDB Global Secondary Indexes with no read activity over the last 30 days. These indexes may still generate storage and write capacity costs, even if the queries they were created for are no longer happening.
Stable also identifies DynamoDB tables that may be better suited to the Standard-Infrequent Access table class. For tables where storage costs dominate and access frequency is low, Standard-IA can help reduce costs.
For teams using provisioned capacity, Stable now detects steady-state DynamoDB usage that may benefit from Reserved Capacity. This allows teams to evaluate whether a one-year or three-year commitment could reduce costs compared with ongoing On-Demand pricing.
OpenSearch recommendations
Stable now flags steady OpenSearch workloads running on On-Demand nodes that may be eligible for Reserved Instances. For domains with consistent usage, a one-year or three-year commitment can significantly reduce hourly costs.
Stable also identifies OpenSearch domains still using gp2 storage. Migrating from gp2 to gp3 can provide higher baseline performance at a lower price per GB, with no downtime and a clear opportunity for immediate savings.
EBS recommendations
Stable now surfaces idle EBS volumes attached to running EC2 instances when very low I/O activity is detected over the last 30 days.
These volumes may still be needed, so Stable does not assume they should be removed automatically. Instead, it flags them for review so your team can validate whether the data is still required before taking action.
CloudTrail and CloudFront recommendations
Stable now flags AWS accounts where CloudTrail events are being duplicated to CloudWatch Logs. While sending CloudTrail events to CloudWatch Logs can be useful for alerting, keeping the full log stream replicated indefinitely can add cost without adding value.
For CloudFront, Stable now identifies distributions where automatic compression is not enabled. Compressing objects at the edge can reduce data transfer volume, lower CloudFront costs and reduce load on the origin.
Stable also detects CloudFront distributions with consistent traffic that may benefit from the CloudFront Security Savings Bundle. This recommendation helps teams evaluate whether a usage commitment, combined with WAF and Shield Advanced coverage, could provide a lower blended rate than On-Demand pricing.
Transfer Family and WAF recommendations
Stable now identifies idle AWS Transfer Family servers with no active connections or file transfer activity over the last 30 days. Because these servers continue to generate hourly charges regardless of usage, idle servers can become a quiet source of waste.
Stable also flags WAF ACL logging configurations that send logs to CloudWatch Logs. For teams that do not need real-time log queries, sending WAF ACL logs directly to Amazon S3 can reduce logging costs substantially.
Built for practical FinOps action
These releases are designed to help teams move from visibility to action.
Microsoft SSO makes it easier to bring the right people into Stable securely. Advanced Filters help teams focus on the recommendations, resources and commitments that matter to their role. The new recommendation checks expand Stable’s ability to detect AWS savings opportunities across more services and usage patterns.
For teams managing growing AWS environments, these updates make it easier to prioritize action, validate savings opportunities and reduce cloud waste without adding manual analysis.
Stable continues to help organizations see where AWS spend is going, understand which opportunities are worth acting on and make better cost decisions with confidence.
See the full release notes
Want the detailed breakdown of each update?
Read the full May 2026 release notes
Read the full June 2026 release notes
Or log in to Stable to explore the latest features and recommendations in your own AWS environment.