Skip to main content

Configure Commitment Management

If you'd prefer to walk through configuring Commitment Management (CM) with nOps, please contact your nOps Sales representative.

If you'd prefer to configure on your own, please follow the steps outlined below.

Prerequisites​

  1. Access to the management account of the AWS Organization
  2. Ability to create and access a new email account or address (using an alias will work)

Create an email address​

In order to enroll in Commitment Management, you will need to create one email address for this purpose under the company domain, such as nops-cm@company.com. If your email service uses aliasing, that will work too. We recommend yourname+cm@company.com in that situation.

Follow your internal process to get access to your nops-cm@ email account.

Add a new AWS account to the AWS Organization​

Login to your AWS management/payer account and follow the steps.

  1. Navigate to the AWS Organization page.

  2. Click on Add an AWS account

  3. Add account information (we recommend Company nOps commitment management for the name) using the new email address and click Create AWS account

Once, you should receive confirmation the new account has been created.

Create a Password for the new AWS account​

  1. Open aws.amazon.com.
  2. Log in as a root user email.
    1. Enter your nops-cm@company.com (or yourname+cm@company.com) email.
    2. Click Next.
    3. Click the Forgot password? link.
  3. Reset your password.

On nOps platform, redirect to commitment management page in Compute Copilot module.

User can see Terraform and CloudFormation method. Lets use terraform method.

Terraform​

We have our own Terraform module for Commitment Management on the Terraform public registry that can be used to finish this configuration, follow the steps below to deploy it on your accounts.

Prerequisites​

  • Terraform v1.2+
  • AWS CLI configured with appropriate permissions

Onboarding child account​

Onboarding child accounts is performed using the same module, it already contains the logic to react when its being applied on any account that is not root. Make sure you're logged in to the new child account and follow the same deployment steps as with the Payer account.

provider "aws" {
  alias  = "child"
}

module cm_onboarding {
  providers = {
    aws = aws.child
  }
  source             = "nops-io/nops-commitment-management/aws"
  # No variables are required to deploy this module on child accounts
}

CloudFormation​

As mentioned in the step 1 , click on Run CloudFormation Stack you will be redirected to the AWS console to run the stack.

Configure the new linked account​

After logging into the linked account, Click on the Run CloudFormation Stack from step 3 or run the following CloudFormation stack

https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/create/review?stackName=nops-sharesave-roles&templateURL=https://s3-external-1.amazonaws.com/cf-templates-1o8svzqapyba5-us-east-1/2023353p12-nops_sharesavev2qp14lq7vf3

When this has completed and the stacks have run successfully, please submit nOps with the following information:

  • Payer account number

And we can complete the configuration process on a short call.