Getting Started
Four steps stand between you and your first AWS savings finding: install the CloudPouch desktop app, register (Free or a 7-day Pro trial), pick an AWS profile, and run a Cost Insight. CloudPouch reads your existing local AWS configuration (the same ~/.aws/credentials and ~/.aws/config files the AWS CLI uses) and installs nothing into your AWS account. Some profiles that work in the AWS CLI need a different configuration for CloudPouch; Credential helpers and role chains lists those shapes.
The journey
Section titled “The journey”For a quick tour of the profile sidebar, Billing, Savings, Compare, and their period controls, start with Application layout.
- Install CloudPouch — download the installer for Windows, macOS, or Linux from cloudpouch.dev, or run
brew install cloudpouchon macOS. - Register your account: CloudPouch opens on its Login screen. Choose Start with a free account, enter your email address, accept the terms, and enter the 6-digit code CloudPouch emails you; your license key then appears in the app. CloudPouch Free is a permanent basic plan, and the Pro trial lasts 7 days with no credit card (see Free and Pro plans).
- Connect an AWS profile: choose one of your existing AWS profiles. Static IAM credentials, AWS SSO profiles, shared
sso-sessionblocks,aws loginprofiles,credential_processhelpers such as aws-vault, and role-chaining profiles all work. - Run your first Cost Insight — press
Cmd/Ctrl + Enterto analyze every eligible AWS service in one bulk run, then review the estimated monthly savings and the per-service totals.
The output is a number you can act on rather than another chart: the estimated monthly saving for the account, broken down per AWS service. CloudPouch Free gives you those totals; CloudPouch Pro adds the Opportunities table — the affected resources, in which regions, and the evidence behind each recommendation (see Free and Pro plans). In one 2021/2022 account, a single EBS Cost Insight run surfaced $18,890/month of GP2-to-GP3 savings.
Before you start
Section titled “Before you start”You need:
- An email address you can receive a 6-digit code at, to register your CloudPouch account.
- An AWS account and a working local AWS profile (the same setup the AWS CLI uses).
- Read permissions for the services you want to analyze — see AWS permissions, or use the ready-made IAM policy. CloudPouch needs no write access — it analyzes your resources but never changes or deletes them.
If your security team needs to approve the tool first, Desktop app vs SaaS and AWS read-only access explain the model: CloudPouch analyzes your AWS data locally through read-only AWS APIs, and there is no vendor-side copy of your cost data. Two paths move data further, and only if you turn them on — enabling the MCP server lets your configured AI assistant read CloudPouch’s local cost and savings data, and an error report you choose to send can include AWS resource names from its redacted log fragment.