Introducing Komiser 3.0
Tags: aws, opensource, devops, cloud
Published: 2023-01-12 15:27:31

Today we are very excited to launch [Komiser v3](https://medium.com/r/?url=https%3A%2F%2Fgithub.com%2Ftailwarden%2Fkomiser), following three months of work since our first beta.

So, what’s new in Komiser?

-   Resource Inventory
-   Tags management
-   Filters
-   Custom views
-   Multi-cloud & accounts support
-   Historical Data

#### Resource Inventory

For the longest time, finding cloud resources has been time-consuming. For example, to find a running instance, you had to go to your cloud provider console, switch to the right cloud account and jump to the service dashboard in the right region where the resource was created. This created a massive needle-in-the-haystack problem for cloud practitioners who needed to find out what resources are being used.

That’s where Komiser comes into play, with its cloud-agnostic resource inventory feature, you can have an active resource inventory of all your running cloud resources across your cloud infrastructure.

![Komiser dashboard](https://cdn-images-1.medium.com/max/800/0*gU-vXOuWHxl3k_vp.png)

#### Tags management

Quickly identify any untagged or improperly tagged resources across multi-cloud accounts and cross regions using simply named operators. Additionally, you can _add_, display, update, and remove _tag_ keys and values from cloud resources.

[Learn why tagging is important.](https://medium.com/r/?url=https%3A%2F%2Fwww.tailwarden.com%2Fblog%2Ftagging-optional)

#### Filters

Easily search and discover your resources using built-in fields and metadata (such as resource name, region, cost, or tags). From the search results, you can quickly navigate to the resources in the appropriate service console and take action (e.g. deleting underutilized resources).

#### Views

We’ve released custom views which serve as a virtual window through which developers can see a filtered list of resources in their cloud infrastructure. You can create multiple views, each presenting an application, team, or project. For example, you can create a view that holds resources associated with your sandbox environment, as identified by tags attached to your resources (e.g. _Environment=sandbox_). Then, you could create a separate view that allows searching only resources in your production environment, based on different values in the tags (e.g. _Environment=production_).

See filters in action:

{% youtube bWTU9UfUxjs %}

#### Multi-cloud & accounts support

Contrary to [AWS Resource Explorer](https://medium.com/r/?url=https%3A%2F%2Faws.amazon.com%2Fabout-aws%2Fwhats-new%2F2022%2F11%2Fannouncing-aws-resource-explorer%2F), which works only on an AWS account scope, not across multiple accounts in an organization. Komiser supports multiple cloud accounts across different cloud providers, including AWS, Oracle Cloud, DigitalOcean, CIVO, Azure, and GCP.

![Komiser support multiple cloud providers](https://cdn-images-1.medium.com/max/800/0*pWwlqrAxQaKvNKby.png)

#### Historical Data

Komiser now persists historical data in SQL databases (we currently support SQLite and Postgres), giving you the ability to write SQL-based queries to explore dynamic data and extend Komiser UI native capabilities.

Stay tuned for some updates on Komiser soon!