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

AWS Onboarding

Learn how to integrate your AWS account with North.cloud

Connect Your AWS Account

Prerequisites:

1

Get your account information ready

AWS Account ID

If your AWS account is part of an AWS organization, please sign up using the billing account only (also called payer account). This will allow North to analyze usage throughout all your accounts and centralize savings opportunities into one view.

AWS Organizational Unit ID

You can find your Organizational Unit ID here.

2

Select your integration method

We recommend using the CloudFormation stack which deploys all the required permissions. We also offer Terraform, CLI, or console commands. Learn more about the permissions.

If you are running the setup manually, make sure to replace the placeholder ADD_ORG_ID_HERE with your Organizational Unit ID as shown here.

  • Click here to open a pre-configured CloudFormation stack in a new tab. This link has a placeholder for your Organizaitonal Unit ID, please add your own.

  • Once in the page, scroll to the bottom and click "I acknowledge".

  • Finally, click "Create stack" to create the stack.

  • Create .tf file

  • Run the following command on the AWS CLI. The code below has a placeholder for your Organizaitonal Unit ID, please add your own.

  • Deploy a CloudFormation stack in the AWS console that will create a read-only cross-account role. This will enable North to recommend the best savings posture based on your usage.

  • In the AWS Management Console, select CloudFormation and “Create Stack”.

  • Select the "Specify an Amazon S3 template URL" and enter the URL below:

  • On the "Specify stack details" page, enter the following information:

    • Stack name: Enter "NorthCloudformationAllFeatures" (or your desired stack name)

    • Click "Next"

    • Click “Create stack”

3

Verify your access

North.cloud will automatically verify your access after your deployment and confirm if your onboarding has been completed successfully. You can also verify manually if any failures happen or need to run the processes asynchronously.

4

Start saving

Once North.cloud completes your savings and data analysis, we'll send you a confirmation email. You'll then have access to all our AI-powered optimization features, the same tools that help leading companies achieve top 1% cloud efficiency.

Update Your North Stack

Update your North stack when North needs a permission that your current stack does not grant. Your North stack is the CloudFormation stack that you deployed during onboarding. The update applies the current North template to your North stack. You will typically need to do this when North releases new features that you may want to use.

Turn on trusted access for CloudFormation StackSets in AWS Organizations before you update your North stack. See the official AWS documentation.

  1. Open CloudFormation in the AWS account and region where you deployed your North stack.

  2. Select your North stack. The default name is NorthCloudformationAllFeatures.

  3. Start an update of the stack.

  4. Replace the current template with this Amazon S3 URL: https://north-cloudformation-template-public.s3.us-east-1.amazonaws.com/billing-and-usage-read-only-cf-stack/north-all-features.yaml

  5. Keep the existing value of the OrgId parameter.

  6. Acknowledge that the stack creates IAM resources.

  7. Review the changes that AWS lists.

  8. Submit the update.

Run the following command on the AWS CLI. If your North stack has a different name, replace NorthCloudformationAllFeatures with that name.

  1. Copy the current Terraform file from the Terraform tab under Select your integration method.

  2. Run terraform apply in the Terraform workspace that you used for your first deployment.

Terraform reads the existing state of that workspace and updates your existing resources. A new workspace tries to create every resource again. That fails, because your Cost and Usage Report bucket already exists.

Member Accounts

Your North stack adds the NorthCloudWatchCrossAccountSharingRole role to each member account in the Organizational Unit that you entered as OrgId. Member accounts that join that Organizational Unit later get the role automatically.

To include an account outside that Organizational Unit, change OrgId to an Organizational Unit ID that contains the account.

Last updated

Was this helpful?