Skip to main content


To configure an AWS Cost Explorer Source:

  1. On the Manage Data > Collection > Collection.
  2. On the Collection page, click Add Source next to a Hosted Collector.
  3. Search for and select AWS Cost Explorer.
  4. Enter a Name for the Source in the Sumo Logic console. The Description is optional.
  5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  6. For Fields, click the +Add link to add custom log metadata. Define the fields you want to associate. Each field needs a name (key) and value.
    • green check circle.png A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema.
    • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the Fields table schema. In this case, an option to automatically add or enable the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo Logic that does not exist in the Fields schema or is disabled it is ignored, known as dropped.

      It is preferable to add an account field (for the dashboards) and assign it a friendly name to identify the corresponding AWS account.
  7. For the AWS Access Key and AWS Secret Key, provide the IAM User access key and secret key you want to use to authenticate collection requests. Make sure your IAM user has the following IAM policy attached with it.
    "Version": "2012-10-17",
    "Statement": [
    "Sid": "VisualEditor0",
    "Effect": "Allow",
    "Action": [
    "Resource": "*"
  8. (Optional) For the Enable Regions field, provide the regions which need to be monitored for cost. The cost incurred across these regions will be fetched separately. The region list here includes all the standard AWS regions along with “global”. “Global” region includes services like Amazon CloudFront, Amazon Route 53, and Amazon IAM. If the field is left empty (default behavior), then data will be fetched from all the enabled regions of the respective AWS account. It is recommended to provide only the regions which are actively used and need to be monitored for cost. This will save the AWS cost for running this source on unused regions.
  9. For the Cost Type, provide supported cost types / MetricTypes. For details on the CostType, see Amazon's Understanding your AWS Cost Datasets: A Cheat Sheet.
    • AmortizedCost
    • BlendedCost
    • NetAmortizedCost
    • NetUnblendedCost
    • UnblendedCost
  10. For Granularity, provide 2 supported granularities for each of the MetricTypes (or cost types):
    • Daily Costs (Polled every 12h)
    • Monthly Costs (Polled every day)
  11. Add Processing Rules.
  12. Click Submit when complete.
Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.