Installation¶
CloudSlash distributes as a standalone binary with zero external runtime dependencies. Select your preferred installation method below:
Quick Install (Recommended)¶
Curl Script¶
Detects your OS and architecture, downloads the correct binary, and creates a cs shortcut alias automatically.
This installs two commands:
cloudslash: the full binary namecs: a symlink alias (shorter to type, works everywhere)
Both are identical. All documentation uses cs for brevity.
Alternative Methods¶
Homebrew (Mac/Linux)¶
After installing via Homebrew, create the alias manually:
Go Install¶
The binary is installed as cloudslash-cli. Rename or alias as needed:
mv $(go env GOPATH)/bin/cloudslash-cli $(go env GOPATH)/bin/cloudslash
ln -sf $(go env GOPATH)/bin/cloudslash $(go env GOPATH)/bin/cs
Initialize¶
Run the init wizard to detect cloud credentials and provision local storage:
The wizard will:
- Run system diagnostics
- Scan for AWS, GCP, Azure, and Kubernetes credentials
- Provision the BadgerDB graph store and S.A.U. state backend
- Generate a
.cloudslash.yamlSlashfile in your current directory
Use --non-interactive for CI environments.
Install Plugins¶
CloudSlash ships as a lightweight core engine. Cloud provider scanners are installed separately. You only install what you need.
# Install the bundled AWS plugin (or cs plugin install aws when published)
cd ../plugins/cloudslash-plugin-aws
cs plugin dev
# See what's available
cs plugin search
# Verify what's installed
cs plugin list
Plugins install into ~/.cloudslash/plugins/ and are discovered on the next scan.
Only install what you need
Only the AWS plugin ships in this workspace. Any other system is a plugin you add later.
Configuration¶
Configuration is stored at ~/.cloudslash/cloudslash.yaml:
cloud:
aws:
active: true
profiles: [production, staging]
pricing:
edp_discount: 0
notifications:
slack:
webhook_url: ""
channel: "#finops-alerts"
Set values with cs config set key=value or edit the file directly.
Installation¶
Verifying Your
This runs adaptive diagnostics: checking only what's relevant to your setup.
Uninstall¶
Removes the graph database, plugins, policies, snapshots, and history. Use --keep-config to preserve your configuration. Use --force to skip confirmation.
# Keep config, remove everything else
cs uninstall --keep-config
# Non-interactive (for scripts)
cs uninstall --force
To also remove the binary itself, follow the instructions printed at the end.