toolsforaws

macOS

Your ~/.aws, organised.

CloudKreds reads and writes the same ~/.aws/config and ~/.aws/credentials the AWS CLI does, and shares its SSO token cache. On top it adds folders, linting, masked diffs, backups, and a per-profile identity test. The companion cloudkreds CLI puts the same resolved credentials into your terminal.

Get CloudKredsOne seat, billed yearly. Pricing on the storefront.

What it does

  • Folders for a file that has none

    Group ninety profiles into something you can navigate, without changing the format the AWS CLI reads.

  • A linter for your config

    Catch the broken source_profile chain, the SSO block missing a region, and the profile that has quietly pointed at a deleted role since March.

  • See the change before you make it

    Every edit is shown as a masked diff against the file on disk, and a backup is taken before it is written.

  • Test the profile, not the syntax

    Resolve any profile and show the account ID and ARN it actually reaches.

  • ckon <profile>

    The CLI activates a profile in the current shell. One eval line in your .zshrc and the whole config becomes reachable from the terminal.

  • Credentials never leave the machine

    Secrets are masked at the snapshot boundary before any data reaches the UI. SSO tokens stay in ~/.aws/sso/cache, compatible with the AWS CLI.

The checkable detail

Resolved credentials carry no Debug or Serialize implementation, so they cannot be logged or sent over IPC. They exist only inside the call stack that resolves them.

Ninety profiles is normal now

Consultants, platform teams, anyone with a client or two: the config file grows until nobody dares edit it. CloudKreds gives it structure without changing a byte the CLI would not understand.

The CLI half is the part you will use every day. ckon prod and the shell is in the right account, with the identity printed so you know it worked.

Every licence includes

Get CloudKreds