Enable Business Analytics

Configure Cost Categories

Required configuration for:

  • Usage-based Cost

  • Unit Cost

  • Profit Margin Analytics

Navigate to Setting > Analytics and set values for the following fields.

  • Compute Cost Source: Select from the dropdown the resource of compute cost. Default: none.

  • Storage Cost Source: Select from the dropdown the resource of data storage cost. Default: none.

  • Archive Cost Source: Select from the dropdown the resource of data archive cost. Default: none.

  • Network Cost Source: Select from the dropdown the resource of network cost. Default: none.

Click Save to save the settings. Selection of these cost categories will be used in usage-based costs, margin analytics as well as unit costs.

For additional configuration specific to a cost source, such as AWS EKS for Compute, follow steps in Enable Data Sources for Cost.

Configure Permissions

Required Configuration for:

  • Profit Margin Analytics

  • Usage-based Cost of Storage, Archive and Network

  • Unit Cost of Storage, Archive and Network

Paigo requires additional cloud platform permissions to calculate various kinds of revenue and cost analytics. Those permissions are all within AWS Cost Explorer. The steps to create an IAM role is documented in Configure IAM Role. Follow the same steps described in that page, but use the permissions.json file below.

permissions.json
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
                "ce:*"
            ],
            "Resource": "*"
        }
    ]
}

Once the role is created, take note of the IAM role ARN.

Navigate to Setting tab and select Analytics subtab from the top. Fill in the IAM Role ARN and External ID just created and click Save to save the new setting.

Enable AWS Cost Allocation Tags

Required Configuration for:

  • Profit Margin Analytics

  • Usage-based Cost of Storage, Archive and Network

  • Unit Cost of Storage, Archive and Network

For several cost and margin analytics, Paigo leverages AWS Cost Allocation Tags to attribute usage to customers. Following these steps to enable AWS cost allocation tags.

  1. Sign in to the AWS Management Console and open the AWS Billing console at https://console.aws.amazon.com/billing/.

  2. In the navigation pane, choose Cost allocation tags.

  3. Select the following tags from the list: paigoCustomerId and paigoDimensionId.

  4. Choose Activate.

See screenshot below for an example.

After you create and apply user-defined tags to your resources, it can take up to 72 hours for the tags to appear on your cost allocation tags page for activation. After you select your tags for activation, it can take up to 24 hours for tags to activate.

If those tags don't appear in the list, then they have never been used by any AWS resources before. First apply those tags on some AWS resources such as EC2 instances or EBS volumes. It may take AWS up to 24 hours to pick up newly created tags on resources.

For detailed documentation of enabling AWS Cost Allocation Tags, see the official documentation User-defined cost allocation tags.

Enable Hourly Cost Data

Required Configuration for:

  • Unit Cost of Storage, Archive and Network

For several unit cost categories, Paigo leverages hourly usage and cost data available in AWS Cost Explorer to calculate. Following these steps to enable Hourly and Resource Level Data.

  1. Sign in to the AWS Management Console and open the AWS Cost Explorer at https://us-east-1.console.aws.amazon.com/cost-management/home#/settings.

  2. In the navigation pane, choose Preference.

  3. Check the box Hourly and Resource Level Data in the Cost Explorer preference.

  4. Click Save preferences at the bottom of the page.

See screenshot below for an example.

Note that Hourly and Resource Level Data has additional cost charged by AWS. Here is the quote from AWS:

a cost of $0.01 per 1,000 UsageRecords-month will be incurred as a result of storing and accessing your hourly- and resource-level information. A UsageRecord is defined as one line of usage. For example, one EC2 instance running for 24 hours will generate 24 distinct UsageRecords at the hourly granularity.

For detailed information on pricing of AWS Cost Explorer, see official documentation AWS Cost Explorer Pricing.

Enable Data Sources for Cost

After choosing the cost source, there are additional steps to perform for each category in order for Paigo to calculate the cost correctly.

Compute Cost on AWS EKS

An agent-based measurement is required for Paigo to collect usage and calculate compute costs. Follow the instructions to deploy agent, label Kubernetes cluster and create agent-based measurement as documented here Agent-based Method .

PreviousUnit Cost for KubernetesNextSandbox

Last updated