The 17.03 release brings the new Impact Dashboard  to the tool. The Impact Dashboard surfaces the results of over 30 compliance checks, displays cloud footprint metrics, calculates savings, and more. This release also introduces Custom Query Filters  which improve bot performance by up to 10x and enable robust filtering within the resource management page. Elasticsearch is also no longer a requirement. After upgrading, this dependency can be removed.

Of note, there are several upgrades with this release that may require changes from your existing installation. Please read Developer/Administrator Notes  for additional information. Release Highlights

• Impact dashboard with interactive widgets
• Resource cost savings visualization and insights over time
• Query filtering system with over 175 filters
• Improved bot filtering and categorization
• Bot filter/action processing performed out-of-band
• Resource tag inspection across entire cloud footprint
• Added support for VPC Connection Peers (AWS)
• Removal of Elasticsearch as a software dependency
• Creating, modifying and deleting Resource Groups is now limited to admin users
• Granting access to resources within Resource Groups is done via the Role permissions system New Filters & Actions
• Network Peer: Filter by account number (whitelist/blacklist)
• Instance: Instance exposes SSH access to the world (0.0.0.0/0)
• Database Instance: Database instance exposes access to the world (0.0.0.0/0)
• Database Instance: Identify low utilization/unused instances by DB connections
• Tags: Six new filters for tag identification including the ability inspect parent tag key/value pairs
• Monthly Cost: Ability to filter on monthly cost for instances and volumes General Improvements
• Resource management page allows searching of common properties including the resource ID, region, and name
• Clouds overview performs server side pagination with search and includes the resource count
• Listing bots performs server side pagination with additional filtering capabilities
• Bot severity surfaced directly in the bot listing
• Bot overview page shows history overview for the last five bot runs
• Resource hookpoints are processed out-of-band
• Slack integration leverages bulk messaging
• Resource tags migrated to separate tablespace for improved performance and easier querying
• AWS CloudWatch data migrated from Elasticsearch to MySQL
• Instance type denormalized and stored directly with the instance
• Resource cost information attributed via the ResourceCommonData table
• CSV download of “My Visible Resources” available
• Updated pricing data for EC2 Developer/Administrator Notes
• After upgrading, bot templates must be re-downloaded from GitHub.
• Negate Filter has been replaced by explicit complement filters in bots. After upgrading, custom bots using Negate Filter are placed in an ‘upgrade’ state and must be upgraded to use the appropriate complement filter.
• When bots are in an ‘upgrade’ state, only their filters/actions can be modified. Scope changes, including resource types and cloud accounts, are not permissible until the bot is upgraded.
• Bot logging into Elasticsearch has been removed. If debug logging is required, we strongly encourage the use of the Log Message action which will output to the standard logs.
• Listing bots via the API now enforces server side pagination for performance reasons. See our API documentation for examples on how to use this endpoint.
• Custom filters will continue to work under the new system, but we strongly encourage migration to the new query filter method, which results in significant performance improvements. Documentation on these filters can be found here.
• Elasticsearch has been removed as a dependency. After running the database migration scripts, you can shutdown/remove this component from your environment.