Skip to main content

AWS Cost Explorer Source


The AWS Cost Explorer Source collects cost and usage reports from AWS Cost Explorer. You have the option to collect from one or more specific AWS cost types and set how often reports are collected.


This source is not available in the Fed deployment.

Data collected

Polling IntervalData
5 minAWS Cost Explorer


Source configuration

When you create an AWS Cost Explorer collector Source, you add it to an existing Sumo Logic hosted collector. Before creating the Source, identify the hosted collector you want to use or simply create a new hosted collector. For further instructions, see Create a Hosted Collector.

To configure an AWS Cost Explorer Source:

  1. In the main Sumo Logic menu, select 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. When you are finished configuring the Source, click Save.

It can take up to 48 hours for AWS to generate your billing data. For accuracy, Sumo Logic does not present any billing analysis for the previous 48-60 hours.

JSON Configuration

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details.

schemaRefJSON Object{"type":"AWS Cost Explorer"}YesDefine the specific schema type.
sourceTypeString"Universal"YesType of source.
configJSON ObjectConfiguration objectYesSource type specific values.

Config Parameters

nameStringYesnullType a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source."mySource"
descriptionStringNonullType a description of the source."Testing source"
categoryStringNonullType a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details."mySource/test"
fieldsJSON ObjectNonullJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.{"_siemForward": false, "fieldA": "valueA"}
accessIDStringYesnullPersonal Access Token from the Asana platform.
accessKeyStringYesnullPersonal Access Token from the Asana platform.
granularityStringYesnullPersonal Access Token from the Asana platform.
costMetricsString arrayYesProvide a list, such as ["AmortizedCost","BlendedCost","NetAmortizedCost", "NetUnblendedCost","UnblendedCost"]
AWS RegionString arrayNoProvide a list, such as ["US East (Ohio)","US West (Oregon)"]

JSON example

"type":"AWS Cost Explorer"

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "AWS_cost_explorer_source" {
collector_id =
schema_ref = {
type = "AWS Cost Explorer"
config = jsonencode({
resource "sumologic_collector" "collector" {
name = "my-collector"
description = "Just testing this"

Download example



Click here for more information about Cloud-to-Cloud sources.

Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.