The CLI works out of the box without any configuration files. On first run, it will:
- Discover AWS profiles from
~/.aws/config - Run an interactive setup to choose profiles and regions
- Create a SQLite database at
~/.ssm/database.db - Run initial sync to discover EC2 instances
Re-run setup anytime:
ssm setupAll application data is stored in ~/.ssm/ (database, cache, etc.)
The CLI automatically discovers available AWS profiles and supports:
- AWS CLI configuration files (
~/.aws/config,~/.aws/credentials) - Environment variables (
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY, ...) - IAM roles and instance profiles
- SSO-based authentication
It scans ~/.aws/config and ~/.aws/credentials to discover configured profiles.
Edit ~/.ssm/config.yaml to customize behavior:
database:
path: ~/.ssm/database.db
aws:
max_concurrent_sessions: 5
discovery:
ttl: 24h