FinOps for Cloud
Sign In
  • Home
  • Open Source
  • FinOps for Cloud
    • Overview
  • Insights
    • Recommendations
      • Savings Optimization Recommendations
      • Security Recommendations
      • Clean-up Scripts Based on Recommendations
      • Archived Recommendations
    • Resources
      • Constraints
    • Pools
      • Configure Assignment Rules
      • Re-apply Ruleset
      • Delete Pools
      • Pool Constraint Policies
    • Cost Explorer
  • Policies
    • Anomaly Detection
      • Create Anomaly Detection Policies
    • Quotas and Budgets
      • Create Quota or Budget Policies
    • Tagging Policies
      • Create Tagging Policies
  • System
    • User Management
    • Data Sources
      • Amazon Web Services
        • AWS Root Account with Data Export Already Configured
        • AWS Root Account With No Data Export Configured
        • AWS Linked
        • Migrate from CUR to Data Exports CUR 2.0
      • Google Cloud Platform
      • Microsoft Azure
    • Events
    • Settings
  • Help and Support
    • Contact Support
    • FAQs
      • Why does the pricing in FinOps not match the SoftwareOne invoice?
    • Release Notes
    • Terms of Use
Powered by GitBook
LogoLogo

Company

  • About SoftwareOne
  • Careers
  • Media Releases

Policies

  • Codes of Conduct
  • Privacy Statement
  • Terms and Conditions

© 2025 SoftwareOne. All rights reserved.

On this page

Was this helpful?

Export as PDF
  1. System
  2. Data Sources
  3. Amazon Web Services

AWS Linked

PreviousAWS Root Account With No Data Export ConfiguredNextMigrate from CUR to Data Exports CUR 2.0

Last updated 11 days ago

Was this helpful?

FinOps for Cloud supports the AWS Organizations service that allows linking several Data Sources to centrally manage the data of multiple users while receiving all billing exports within a single invoice.

Selecting AWS Linked makes the registration flow easier, eliminating the option to input bucket information for billing purposes. Bucket information is received through the root account, whose user can distribute periodic reports individually if intended by the company management.

Provide the AWS access key ID and AWS secret access key, and click Connect to create a Data Source in FinOps. If the provided values are invalid, an error message is displayed.

If you only specify an AWS-linked account without providing credentials for the main one, FinOps for Cloud won't be able to import any billing data.

Discovering resources

FinOps for Cloud needs to have permissions configured in AWS for the user Data Source to correctly discover resources and display them under a respective section of the dashboard for the associated employee.

Make sure to include the following policy for FinOps to parse EC2 resource data:

{
	"Version": "2012-10-17",
	"Statement": [
		{
			"Sid": "FinOpsforCloudOperations",
			"Effect": "Allow",
			"Action": [
				"s3:GetBucketPublicAccessBlock",
				"s3:GetBucketPolicyStatus",
				"s3:GetBucketTagging",
				"iam:GetAccessKeyLastUsed",
				"cloudwatch:GetMetricStatistics",
				"s3:GetBucketAcl",
				"ec2:Describe*",
				"s3:ListAllMyBuckets",
				"iam:ListUsers",
				"s3:GetBucketLocation",
				"iam:GetLoginProfile",
				"cur:DescribeReportDefinitions",
				"iam:ListAccessKeys",
				"elasticloadbalancing:DescribeLoadBalancers",
				"elasticloadbalancing:DescribeTags"
			],
			"Resource": "*"
		}
	]
}

Your AWS Data Source is ready for integration with FinOps for Cloud.

AWS Linked option on the Connect Data Source page