Skip to content

Managing AWS Accounts

Integrating your AWS accounts with Spend Shrink is essential to gain a comprehensive understanding of your cloud spending and uncover actionable optimization opportunities. This guide outlines the steps for connecting both standalone and organization-linked accounts, ensuring a seamless setup process.


Table of Contents

  1. Overview
  2. Enabling Cost Explorer
  3. Using the Connection Wizard
  4. Assumable Role
  5. Access Keys
  6. Standalone Accounts vs. Organizations
  7. Recommendations
  8. Terraform
  9. Support

Overview

To maximize the value of Spend Shrink, it is critical to connect all your AWS accounts, including:

  • Standalone accounts.

  • Organization payer accounts and linked accounts.

By integrating all accounts, you achieve full visibility into your cloud spending, resource utilization, and potential optimization opportunities.


Enabling Cost Explorer (Required)

Why Cost Explorer is Required

Spend Shrink relies on AWS Cost Explorer to access accurate cost and usage data for your accounts. Without enabling Cost Explorer, Spend Shrink cannot provide accurate analysis or recommendations.

Steps to Enable Cost Explorer

  1. Log in to the AWS Management Console.
  2. Navigate to Billing > Cost Explorer.
  3. Click Enable Cost Explorer.

Important Details

Cost Explorer must be enabled at the payer account level for AWS Organizations and for any standalone accounts not part of an organization. Linked accounts usually inherit from the payer account so generally do not need to be enabled at the account level, however, you should always verify that cost explorer is enabled for each account as we require this for accessing accurate cost and billing data.

It can take up to 72 hours for AWS to process and backfill historical spend data. Initial results may be incomplete during this time, but Spend Shrink will automatically reprocess data every 24 hours to ensure accuracy.

Usage Costs:

AWS Cost Explorer incurs a small usage fee (typically $XX USD per month per AWS account). These costs are billed by AWS and are the responsibility of the customer.


Using the Connection Wizard

Spend Shrink’s Connection Wizard streamlines the process of connecting AWS accounts. Choose one of the following secure methods based on your organization's preferences:

  1. Select the Assumable Role option in the wizard.
  2. Deploy the role using either the CloudFormation button in our wizard or manually via Terraform (alternative method mentioned below)
  3. To automatically deploy, log in to AWS with an admin account in another browser tab and then press the deploy button in our wizard
  4. Follow the steps and allow CloudFormation to build the stack, then check the Cloud Formation stack outputs for the created role ARN.
  5. Provide the newly created Role ARN
  6. Click Add Account to finalize the process.

Access Keys (Legacy)

We highly recommend using the assume role method instead as its inherently more secure and avoids issues like stale credentials or personal user access keys being used.

  1. Select the Access Keys option in the wizard.
  2. Enter the Access Key ID and Secret Access Key.
  3. Ensure the access keys are associated with a user having the required permissions:
  4. Grant exactly the actions listed under Permissions below.
  5. Click Add Account to complete the integration.

Standalone Accounts vs. Organizations

Spend Shrink supports both standalone AWS accounts and accounts within AWS Organizations:

  • Standalone Accounts: These are accounts not part of an AWS Organization. Each account must be added individually through the wizard.
  • AWS Organizations: For accounts under an organization, connect the payer account and all linked accounts to gain full visibility into consolidated billing and usage. The payer account's billing export already includes every linked account's charges, so each charge is counted once: when the payer account is in your scope, linked-account costs come from its export, and a linked account's own export is used only when its payer account is not connected. Connecting linked accounts still matters for resource details and recommendations, which each account's read-only role collects.

Best Practice: Add both the payer and all linked accounts to ensure Spend Shrink provides the most accurate and actionable insights. Omitting linked accounts may result in incomplete data and missed opportunities for optimization.


Recommendations

To achieve the most comprehensive insights, we recommend: - Adding all AWS accounts, including both payer and linked accounts. - Using the Assumable Role method whenever possible for enhanced security and scalability. - Regularly reviewing your connected accounts to ensure all active accounts are integrated.


Permissions

The connection wizard deploys one CloudFormation template, spendshrink-connect.yaml. It creates the SpendShrink role, a bucket you own for the FOCUS billing export, and the export itself. The role can only be assumed by SpendShrink's AWS account with your account's External ID.

The list below is generated from that template on every change, so it always matches what the role grants. Almost every action is a Get, List or Describe call. The exception is bcm-data-exports:CreateExport, which lets SpendShrink set up the billing export in your account. The role cannot start, stop, resize or delete anything, and it can read objects only under the spendshrink-focus/ prefix of the bucket the stack created.

The role grants 53 IAM actions (template version 2026-10-21-w29). Every action is listed by its exact name; there are no wildcards and no AWS managed policies.

Statement Actions Condition
IdentityAndOrganization organizations:DescribeOrganization
organizations:ListAccounts
sts:GetCallerIdentity
always
FocusExportDiscoveryAndProvisioning bcm-data-exports:CreateExport
bcm-data-exports:GetExport
bcm-data-exports:ListExports
always
ReadFocusObjects s3:GetObject always
ListFocusObjects s3:ListBucket always
ComputeInventory autoscaling:DescribeAutoScalingGroups
ec2:DescribeAddresses
ec2:DescribeInstances
ec2:DescribeNatGateways
ec2:DescribeRegions
ec2:DescribeSpotPriceHistory
ec2:DescribeVolumes
elasticloadbalancing:DescribeInstanceHealth
elasticloadbalancing:DescribeLoadBalancers
elasticloadbalancing:DescribeTags
elasticloadbalancing:DescribeTargetGroups
elasticloadbalancing:DescribeTargetHealth
rds:DescribeDBInstances
rds:DescribeReservedDBInstances
always
ContainerInventory ecr:DescribeImages
ecr:DescribeRepositories
ecr:GetLifecyclePolicy
eks:DescribeCluster
eks:DescribeFargateProfile
eks:DescribeNodegroup
eks:ListClusters
eks:ListFargateProfiles
eks:ListNodegroups
always
StorageInventory s3:GetBucketLocation
s3:GetBucketTagging
s3:GetBucketVersioning
s3:GetLifecycleConfiguration
s3:ListAllMyBuckets
always
UtilizationMetrics cloudwatch:GetMetricData
cloudwatch:GetMetricStatistics
cloudwatch:ListMetrics
always
CostOptimizationHubDetectors cost-optimization-hub:GetRecommendation
cost-optimization-hub:ListRecommendations
always
ComputeOptimizerDetectors compute-optimizer:GetAutoScalingGroupRecommendations
compute-optimizer:GetEBSVolumeRecommendations
compute-optimizer:GetEC2InstanceRecommendations
compute-optimizer:GetECSServiceRecommendations
compute-optimizer:GetEffectiveRecommendationPreferences
compute-optimizer:GetEnrollmentStatus
compute-optimizer:GetLambdaFunctionRecommendations
compute-optimizer:GetRDSDatabaseRecommendations
always
CommitmentPlanningDetectors ce:GetCostForecast
ce:GetReservationPurchaseRecommendation
ce:GetSavingsPlansPurchaseRecommendation
always
CostExplorerHistoryImport ce:GetCostAndUsage only when HistoryImportEnabled

If you build the role yourself (for example with Terraform), grant exactly these actions and keep the External ID condition on the trust policy. Broader policies such as ReadOnlyAccess are not needed.

Updating your stack

When we add a permission, the AWS Accounts page shows Stack update available (everything keeps working; an upcoming feature needs the new permissions) or Stack update required (the account shows Action required and readiness reports pause until you update). Click the chip, prepare a fresh setup, and SpendShrink shows the exact aws cloudformation update-stack command for your stack. It replaces the template and the External ID and keeps every other parameter. Then verify the same role ARN to finish.


Support

If you encounter any challenges while adding AWS accounts, our team is here to help:

  • Contact us directly at support@spendshrink.com

Begin your integration today to unlock the full potential of Spend Shrink for your cloud cost optimization strategy.