For the complete documentation index, see llms.txt. This page is also available as Markdown.

AWS permissions

Permissions North.cloud requires from your AWS account.


IAM Permission & Deployment

North requires carefully scoped IAM permissions so our application can access cost and usage data required by our ML engine to provide automated FinOps recommendations. We purposefully limit all permissions to the minimum necessary for your financial analysis and do not request access to your workloads or sensitive application data.

During onboarding, you have the option to add an external ID to the IAM roles assigned to your unique North root user. Using an external ID is an AWS security best practice. This externally supplied secret string helps ensure that only North’s authorized systems can assume the roles you configure. It is optional, but we encourage its use for additional protection. North will provide the required external ID value (if you choose to use it) securely during onboarding as part of our recommended implementation.

If you add an external ID, it must match the value North holds for your account. If the two values differ, North's daily verification check fails, and your cost data pauses until they match. To get an external ID, ask your North Customer Success contact.

What North CAN NOT do:

  • Read sensitive data from your workloads or databases

  • View or edit network rules and security groups

  • Create, modify, stop, or terminate any compute instances or other machines

  • Change, copy, or export any development, test, or production data

The following sections explain the IAM permissions required, why each group is needed.

Groups 1 to 3 are not a menu. They describe what is inside a single CloudFormation stack. Whichever method you use to onboard, console, CLI, or Terraform, you deploy the same north-all-features.yaml template, and it carries all three groups together. The grouping below explains what that one stack grants and why, so you can review it before you deploy it. Group 4, Auto-Purchasing, is the exception. It is a separate role you deploy separately, and only if you want it.


Permission Groups Explained

1. Baseline (Default) – Read-Only Cost & Usage Data

Purpose: These permissions are required for North to read AWS billing, usage, and cost details, which underpin all FinOps analysis and recommendations.

Key Actions Explained:

  • ce:Get* – Read cost, usage, and commitment data from AWS Cost Explorer.

  • ce:StartSavingsPlansPurchaseRecommendationGeneration – Start the generation of Savings Plans purchase recommendations in Cost Explorer.

  • Explicitly read-only: No permission to change or stop resources.

Policy Example:


2. Premier Baseline – Organization Accounts, EBS Volumes & Lambda Concurrency

Purpose: These permissions let North list the accounts in your organization and read the configuration of your EBS volumes and Lambda provisioned concurrency. Rightsize reads CloudWatch metrics through NorthCloudWatchCrossAccountAccessRole and NorthCloudWatchCrossAccountSharingRole, described in Advanced Permissions, below.

Key Actions Explained:

  • organizations:ListAccounts – List the accounts in your organization.

  • ec2:DescribeVolumes – Read the configuration of your EBS volumes.

  • lambda:ListProvisionedConcurrencyConfigs – Read the provisioned concurrency settings of your Lambda functions.

Policy Example:

In summary: These permissions are read-only. North uses them to list your accounts and to read the configuration of the resources that Rightsize analyzes.


3. Advanced Permissions – Cross-Account, Cross-Region, CUR Read Access & Enhanced Real-Time Metrics

Purpose: These permissions are required (not optional) for customers who want access to North’s advanced FinOps and optimization features. They let North retrieve detailed Cost & Usage Report (CUR) data for hourly, resource-level cloud visibility. They also let North ingest granular metrics from CloudWatch. This deeper and more real-time data access powers advanced analytics, fine-grained savings opportunities, and our most precise rightsizing and recommendation features.

Without these advanced permissions, North cannot provide resource-level breakdowns, high-frequency cost analysis, or evaluate metrics on specific resource behaviors necessary for state-of-the-art optimization.

Why are these permissions necessary?

  • CUR (Cost & Usage Report) bucket read access (s3:GetObject, s3:ListBucket): This is essential for North to ingest detailed, hourly, and resource-level usage data from your AWS-generated reports. These permissions give you the granularity you expect from modern cloud cost tooling and inform North's advanced dashboards and recommendation engine.

  • CloudWatch cross-account metric and real-time data access (cloudwatch:GetMetricData, sts:AssumeRole): These permissions let North access the specific metrics required for analysis and rightsizing, across your AWS accounts and regions. North uses these metrics for real-time analytics and more accurate optimization suggestions.

  • S3 write-like actions (s3:PutObject): The bucket policy grants this permission to AWS billing, which delivers your Cost and Usage Reports to the bucket. North has no write access to the bucket.

Key Actions Explained:

  • sts:AssumeRole: Enables North to securely access metric and cost data from linked accounts, supporting organizations with multi-account structures. You can add an external ID to protect your account from unauthorized role assumptions. To get one, ask your North Customer Success contact.

  • cloudwatch:GetMetricData: Enables retrieval of highly specific CloudWatch metrics for North’s analytics. It is strictly read-only and always scoped to the required metrics for insight and rightsizing.

  • s3:GetObject, s3:ListBucket: Let North read your AWS Cost & Usage Reports directly from S3. North uses this report data for hourly, resource-level cost detail.

  • s3:GetBucketTagging, cloudformation:DescribeStacks, cloudformation:DescribeStackEvents, cloudformation:ListStackResources, cloudformation:GetTemplate: Let North read the tags of your Cost and Usage Report bucket and the details of your North stack. North uses them to identify the template version you deployed. The CloudFormation permissions apply to your North stack only.

  • ec2:DescribeVolumes, lambda:ListProvisionedConcurrencyConfigs: Let Rightsize read the configuration of EBS volumes and Lambda provisioned concurrency in each account.

  • s3:GetLifecycleConfiguration, s3:GetBucketVersioning, s3:GetReplicationConfiguration, s3:GetIntelligentTieringConfiguration, s3:GetBucketRequestPayment: Let Rightsize read the lifecycle, versioning, replication, Intelligent-Tiering, and Requester Pays settings of your S3 buckets. These permissions do not give access to the objects in your buckets.

Policy Examples:

These permissions sit on two roles and one bucket. Each role has a trust policy, which states who can use the role, and a permission policy, which states what the role can do. The Cost and Usage Report bucket has its own bucket policy. In each example, <your-account-id> is the ID of the management account where you deploy the stack.

NorthCloudWatchCrossAccountAccessRole trust policy.

NorthCloudWatchCrossAccountAccessRole permission policy. The NorthReadStack statement below contains the default stack name, NorthCloudformationAllFeatures. If your North stack has a different name, the statement contains that name. A Terraform deployment does not include the NorthReadStack statement.

NorthCloudWatchCrossAccountSharingRole trust policy. The stack creates this role in your management account. A StackSet creates it in each account in the organizational unit you select.

NorthCloudWatchCrossAccountSharingRole permission policy. In member accounts, the first statement also includes lambda:ListProvisionedConcurrencyConfigs.

Cost and Usage Report bucket policy. The first statement lets AWS deliver your reports to the bucket. The second lets NorthCloudWatchCrossAccountAccessRole read them.

In summary: These advanced permissions are required for North’s resource-level and real-time recommendations. They are always used in a secure, read-only, and compliance-focused manner, never for broad resource access or uncontrolled data export.


4. Auto-Purchasing (Optional) – Buying Commitments in Your Own Account

Purpose: Everything above is read-only. It lets North recommend commitments. It does not let North buy them. Autobot needs a separate role, NorthAutoPurchasingRole, before it can purchase commitments directly in your own AWS account.

This role is optional and separate from the onboarding stack. Grant it only if you want Autobot to purchase on your behalf. North verifies it separately, and a missing purchasing permission does not affect your account's overall verification status.

Trust policy. The role trusts one named role inside North's account, not North's account root.

This role does not take an external ID, and it does not need one. An external ID exists to remove ambiguity when a trust policy lists a whole account as the principal. This trust policy lists a single role, NorthAutoOrchestratorRole, so there is no ambiguity to remove. Do not add an sts:ExternalId condition to it. The external ID described at the top of this page applies to the cost and usage roles only.

Permission policy. Each statement pairs the read-only Describe actions North uses to price an offering with the single purchase action for that commitment type.

The OpenSearch statement uses the es: prefix. OpenSearch kept that IAM namespace after AWS introduced the newer API name, so es: is correct here.


Supported Customizations

Some organizations change the roles or the StackSet in north-all-features.yaml to meet their own security policies. The table lists the changes North supports for the cost and usage roles and for NorthCloudWatchStackSet. For any other change, ask your North Customer Success contact before you deploy it.

Change
Supported
What to know

Add an aws:ResourceOrgID condition so that NorthCloudWatchCrossAccountAccessRole can assume sharing roles only in your organization

Yes

-

Use a different name for the CUR bucket

Yes

Send the bucket name to your North Customer Success contact, and North configures your account with it. The default name, north-cur-bucket-<account-id>, is preferred.

Encrypt the CUR bucket with your own KMS key

No

Keep the default SSE-S3 encryption (AES256). If North cannot decrypt your reports, your cost data stops arriving.

Trust named North roles in NorthCostAndUsageRole and NorthCostAndUsageRolePremium

No

Keep North's account root as the principal, with an external ID if you use one. The North roles that assume these roles change as North releases new features.

Deploy NorthCostAndUsageRolePremium in a member account

No

Deploy it in your management account, with the rest of the stack.

Turn off automatic deployment on NorthCloudWatchStackSet

Yes

You add each new account to the StackSet yourself. Read the note below this table before you make the change.

A note on turning off automatic deployment. NorthCloudWatchStackSet creates NorthCloudWatchCrossAccountSharingRole in each account in the organizational unit you select. With automatic deployment on, AWS also creates the role in each account that joins that organizational unit later. If your policies require an approval for each new role, you can turn automatic deployment off. If you do, the following applies:

  • North cannot read CloudWatch metrics or S3 bucket settings in a new account until you add that account to the StackSet. Until then, Rightsize excludes resources in that account from recommendations when it cannot read their metrics. A warning on the Rightsize page lists the affected member accounts. Turning off automatic deployment does not affect your cost data for that account, because North reads it from your Cost and Usage Report.

  • Add each new account to the StackSet as a stack instance. AWS then applies each North template update to that account together with your other accounts. AWS does not apply template updates to a role that you create by hand.

  • If you turn automatic deployment back on, AWS adds the role only to accounts that join after that. Add the accounts that joined while it was off to the StackSet yourself.

  • Make the change in the file that you deploy. In north-all-features.yaml, set Enabled to false under AutoDeployment. In Terraform, set enabled = false under auto_deployment. Each new North template has automatic deployment on, so make the change again each time you update your North stack.


Important Security Best Practices

  • Always review permissions and restrict to least-privilege required for your use case and feature set.

  • Avoid granting broad, unnecessary permissions such as "ec2:Describe*" to any third party, including North.

  • If you have questions on what each permission is used for, please contact our support team for a granular explanation.

  • If you want additional protection, you may use an external ID in your trust relationship when granting North cross-account role access.

By adhering to these permission designs, you retain control and visibility into what North can access, and ensure your AWS environment stays secure and optimized.


Note: Any required North account ID, role ARNs, and (optionally) external IDs can and will be provided securely to you by North during onboarding.

Last updated

Was this helpful?