Skip to content

Create a CloudPouch IAM policy

CloudPouch needs only read-oriented IAM permissions: ce:GetCostAndUsage for billing data plus describe/list actions for the AWS resources its Cost Insights inspect. It never writes to your AWS account and installs no infrastructure in it — the app runs entirely on your desktop and talks to AWS the same way the AWS CLI does.

You have three ways to grant access. Most SSO users need no setup at all.

Option 1: Reuse an existing profile or role

Section titled “Option 1: Reuse an existing profile or role”

CloudPouch reads the same local AWS configuration (~/.aws/config and ~/.aws/credentials) as the AWS CLI. If your existing profile, SSO role, or assumed role can already read Cost Explorer data and resource metadata — which is true for most admin, power-user, and read-only roles — just select that profile in CloudPouch and start analyzing. This is the usual path for AWS SSO (IAM Identity Center) setups.

The profile needs to read:

  • AWS Cost Explorer data (ce:GetCostAndUsage, plus ce:GetTags for the Bedrock tag breakdown).
  • AWS Organizations account names (organizations:ListAccounts), if you analyze a payer account and want account names instead of IDs.
  • Resource metadata for the Cost Insights you plan to run — for example ec2:Describe* for EC2, EBS, Elastic IP, and NAT Gateway insights, or rds:Describe* actions for RDS.

If you prefer a dedicated identity, create an IAM policy from the full JSON in AWS permissions and attach it to the IAM user or role behind your local AWS profile. The policy is one statement of read-only Get*/List*/Describe* actions against Resource: "*" — access is limited by the action list, not by resource ARNs.

Security-conscious teams can start from that policy and narrow it — but not by deleting whatever the permission diagnostics never mention. A call that succeeds produces no permission error, so an action’s absence from that list is not evidence that CloudPouch did not use it. Work the other way round: attach a candidate restrictive policy, run a Savings Scan, investigate the operations that failed, verify their IAM actions and the permissions those depend on, then retest across the AWS services and resource configurations you need to cover.

CloudPouch provides an optional CloudFormation stack that creates the policy for you:

  • Stack name: CloudPouch-access-policy-stack
  • Created policy name: CloudPouch-costs-policy

The stack creates an IAM policy and nothing else — it is a setup convenience, not CloudPouch runtime infrastructure. After the stack completes, attach CloudPouch-costs-policy to the IAM user or role your AWS profile uses. The stack’s policy may not yet include actions for the newest Cost Insights, so compare it against the AWS permissions baseline and add anything missing. CloudPouch’s permission issue details name the AWS API operation that failed, with its service, region, and error code; map that operation to the corresponding IAM action yourself, because an API operation does not map one-to-one onto an IAM action.

If you use a plain IAM user:

  1. Open the IAM Users page in the AWS console.
  2. Select the user behind your local AWS credentials.
  3. Choose Add permissions, then Attach policies directly.
  4. Search for CloudPouch-costs-policy (or your manually created policy).
  5. Select it and add it to the user.

If you use an IAM role or an SSO permission set, attach the equivalent permissions through your normal access-management workflow instead.

  1. Open CloudPouch and select the AWS profile.
  2. Run any Cost Insight — EBS is a good first test. It reads EC2 volume metadata and cost data, plus CloudWatch metrics, which the EBS volume-type recommendations depend on.
  3. If something is missing, CloudPouch lists the failed AWS API operation with its service, region, and error code (such as AccessDenied). Verify the matching IAM action and any permissions it depends on before changing the policy, and bear in mind the list covers only the operations that particular run reached.