Onboard Commitment Manager with Terraform

Commitment Manager automation is supported on management and standalone accounts.

You can onboard Commitment Manager with creating a new CUR or using an existing CUR.

Create a new CUR

module "zesty_account" {

  source  = "zesty-co/zesty-account/aws"

  version = "~> 0.1.1"

  account_type = "management"

  cm = {}

}

This configuration:

• Creates one Zesty IAM role and policy

• Adds Commitment Manager automation permissions to the policy

• Creates a CUR v1 report and private S3 bucket by default

• Registers Commitment Manager for the account

Commitment Manager is not supported on linked accounts.

Use an existing CUR

For a management or standalone account, the module can use a customer-owned CUR instead of creating a new report and bucket.

module "zesty_account" {

  source  = "zesty-co/zesty-account/aws"

  version = "~> 0.1.1"

  account_type = "management"

  cm = {}

  cur = {

    mode        = "existing"

    type        = "cur_v2"

    s3_bucket   = "customer-cur-bucket"

    export_name = "customer-cur-export"

  }

}

The module does not create or take ownership of the supplied bucket or report. It grants the Zesty role access to the named bucket and sends the CUR details to Zesty.

Use:

• cur_v1 for a legacy Cost and Usage Report.

• cur_v2 for AWS Data Exports/CUR 2.0.

Important

• The module can create CUR v1 only. Use mode = "existing" for CUR v2.

• Management-account Kompass onboarding currently requires a CUR v1-compatible Athena layout.

• If you want to use an existing CUR 2.0 export with management-account Kompass, contact Zesty Support before applying the configuration.