Starting from Komiser v3 and beyond, you 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
Cloud provider account configuration is done through the config.toml file, using either the
CREDENTIALS_FILE. Komiser now supports multiple cloud accounts by default.
Once added the credentials to your cloud provider accounts you will want to choose between these two methods of persisting your AWS Account data.
Add to config.toml file
postgresand a database
komiseron the local Postgres server.
# Add to config.toml file [sqlite] file = "komiser.db"
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.
[[aws]] name="sandbox" source="CREDENTIALS_FILE" path=./path/to/credentials/file profile="default" [[aws]] name="staging" source="CREDENTIALS_FILE" path=./path/to/credentials/file profile="staging-account" [[gcp]] name="production" source="ENVIRONMENT_VARIABLES" # path=./path/to/credentials/file specify if CREDENTIALS_FILE is used profile="production" [postgres] uri="postgres://postgres:komiser@localhost:5432/komiser?sslmode=disable"
Usage: komiser start [command]
Available Commands: config Create configuration file help Help about any command start Run Komiser server version Show tool version Flags: -h, --help help for komiser
Once you have correctly build your config.toml file, in the same directory, run the command:
Point your browser to http://localhost:3000
Komiser is also available as a Docker image:
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.tomlfile, 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
-vflags as seen in the
Docker runcommand below.
docker run -v /local/path/to/config.toml:/etc/config/config.toml -v /local/path/to/credentials.yaml:/etc/config/credentials.yaml -d -p 3000:3000 --name komiser tailwarden/komiser:latest komiser start --config /etc/config/config.toml
Docker installation tutorial
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.