Komiser

The current policy.json has a lot of wildcards and also lacks a few resources that we have started to support lately. https://github.com/tailwarden/komiser/issues/852

https://github.com/tailwarden/komiser/issues/801

Developers can create custom views and set up Slack alerts to monitor resource costs and usage, without spending all day monitoring the views. However, Slack may not always be the primary collaboration tool for developers. Additionally, receiving an alert is not the end goal, as certain actions are triggered when specific alerts are received, such as creating a ticket on Jira/Linear to be tackled by the infrastructure team, triggering an alert on an incident & response platform like PagerDuty, or even running a custom script to resize the infrastructure.

Users can currently connect one or many cloud accounts from the nine supported cloud providers through a config.toml file. However, this requires users to have knowledge of config file syntax, as well as an understanding of what permissions they need to assign to Komiser in order for it to fetch their asset inventory. We have received numerous issues in our GitHub repository and Discord community regarding this process of connecting a cloud account.

As an organization, you run critical applications on the cloud, and the infrastructure that runs those critical applications can be spread across different accounts and have complex relationships. When you want to understand the landscape of your existing setup, it can seem daunting to go through lists of resources and try to understand how the resources are connected. It would be useful if you had an easier way to visualize everything.