Quickstart
Komiser configurations
Starting from Komiser v3 and beyond, your komiser configuration which holds the credentials to your cloud providers is defined through a config.toml file. When you position the config.toml file within the same directory as the Komiser binary, it will be automatically detected. However, if you choose to place it in an alternate location, you can do so and then provide the path using the --config
flag.
Example start
command
Config.toml file
Cloud provider account configuration is done through the config.toml file, using either the ENVIRONMENT_VARIABLES
or CREDENTIALS_FILE
. Komiser now supports multiple cloud accounts by default.
Data persistence
Once added the credentials to your cloud provider accounts you will want to choose between these two methods of persisting your AWS Account data.
Postgres
Add to config.toml file
postgres
and a database komiser
on the local Postgres server. SQLite
The reason for this external data persistence is to improve the filtering, sorting and tagging management experience making it faster and smoother. It also serves as a standalone DB which you are free to query and visualize as you see fit.
Example config.toml
Options
Once you have correctly build your config.toml file, in the same directory, run the command:
Point your browser to http://localhost:3000
Docker
Komiser is also available as a Docker image:
https://hub.docker.com/r/tailwarden/komiser/tags/
Check Docker Hub of the Komiser changelog to find the latest version of Komiser.
Note: From Komiser v3 onwards, we natively support multiple cloud account authentication through the
config.toml
file, you will need to mount this fill along with a credentials file (not needed is using ENVIRONMENT_VARIABLES as the auth source) to the Docker container using the-v
flags as seen in theDocker run
command below.
Docker installation tutorial
Self-hosted
Head over to your cloud provider of choice to learn how to connect your Komiser CLI to your cloud account and to deploy a self hosted version of the tool.