Create a CUR for Kompass integration

Prev Next

This topic describes how to enable a legacy AWS Cost and Usage Reports (CUR) specifically for the purpose of integrating your K8s environment with Kompass.

To create a legacy CUR for other purposes, see Create a legacy CUR.

A CUR is needed for these AWS accounts:

  • The Member account with the EKS cluster that was integrated for the POC (must)
    This account was formerly known as the subaccount.

  • The Management account (highly recommended)
    This account was formerly known as the Master account.

    A CUR for the Management account can give you visibility to all of your AWS resources.

If either account has an existing CUR that matches all the configurations below, you can use that CUR instead of creating a new one. For the Management account, that CUR needs 90 days of data. You can backfill data into a CUR as described in Backfill data into a CUR.

Prerequisites

  • AWS permissions to create a legacy CUR for both the Member and Management accounts

Note that AWS can take 24+ hours to generate the first CUR.

To create a CUR:

You will run this procedure twice. First for the Member account with the EKS cluster and then for the Management account.

  1. Log in to the AWS Management Console for the Member account (formerly known as subaccount).

  2. From the AWS console, go to Billing and Cost Management.

    You can find that using the search bar.

  3. In the left menu, under Cost Analysis, select Data Exports.

  4. Click Create.

    The Create export page is displayed. On this page you customize the CUR with the criteria required by Zesty.

  5. Customize the CUR:

    The following screenshot shows a completed configuration with marked sections that match the following described steps:

    1. For Export type, select Legacy CUR export.

    2. For Export name, type a name.

      We recommend a name like zesty-<yourbusinessname> that is unique and easily identifiable.

    3. In the Export content section, for Additional export content, select Include resource IDs.

      Leave Data refresh settings blank.

    4. In the Data export delivery options section, select the following:

      1. For Report data time granularity, select Hourly.

      2. For Report versioning, select Overwrite existing.

      3. For Report data integration, select Amazon Athena.

        For Compression type, leave the default selection, Parquet, selected.

    5. In the Data export storage setting section, click Configure.

      The Configure S3 bucket dialog is displayed.

    6. In the Configure S3 bucket dialog, either create or select an existing S3 bucket for CUR data, then confirm the bucket configuration.

      On the Create export page, your S3 bucket name is now displayed.

    7. (Optional) Add an S3 path prefix.

      The path prefix enables organization and structure within the S3 bucket.

    8. (Optional) You can add tags.

    9. Click Create report.

  6. Repeat this process for the Management account (formerly known as the Payer account).

  7. For the Management account only:

    When you have received confirmation of the CUR being initiated, backfill 3 months of data into the new CUR as described in Backfill data into a CUR.

After creating the CUR, contact your Zesty representative.

After creating a CUR, AWS automatically uploads the crawler-cfn.yml file to your CUR S3 bucket. This file contains the resources that are necessary to set up Glue Crawlers and databases for Athena.

Example location: s3://<your-bucket>/cloudformation/crawler-cfn.yml

If there are issues in creating the CURs or other resources (such as the crawler file), reach out to your Zesty representative.