Skip to content

Latest commit

 

History

History
55 lines (46 loc) · 1.68 KB

docs.asciidoc

File metadata and controls

55 lines (46 loc) · 1.68 KB
Raw

You can monitor your estimated AWS charges by using Amazon CloudWatch and Cost Explorer.

This aws billing metricset collects metrics both from Cloudwatch and cost explorer for monitoring purposes.

AWS Permissions

Some specific AWS permissions are required for IAM user to collect estimated billing metrics.

cloudwatch:GetMetricData
cloudwatch:ListMetrics
tag:getResources
sts:GetCallerIdentity
iam:ListAccountAliases
ce:GetCostAndUsage
organizations:ListAccounts

Dashboard

The aws billing metricset comes with a predefined dashboard. For example:

metricbeat aws billing overview

Configuration example

- module: aws
  period: 24h
  metricsets:
    - billing
  credential_profile_name: elastic-beats
  cost_explorer_config:
    group_by_dimension_keys:
      - "AZ"
      - "INSTANCE_TYPE"
      - "SERVICE"
    group_by_tag_keys:
      - "aws:createdBy"

Metricset-specific configuration notes

When querying AWS Cost Explorer API, you can group AWS costs using up to two different groups, either dimensions, tag keys, or both. Right now we support group by type dimension and type tag with separate config parameters:

  • group_by_dimension_keys: A list of keys used in Cost Explorer to group by dimensions. Valid values are AZ, INSTANCE_TYPE, LINKED_ACCOUNT, OPERATION, PURCHASE_TYPE, REGION, SERVICE, USAGE_TYPE, USAGE_TYPE_GROUP, RECORD_TYPE, OPERATING_SYSTEM, TENANCY, SCOPE, PLATFORM, SUBSCRIPTION_ID, LEGAL_ENTITY_NAME, DEPLOYMENT_OPTION, DATABASE_ENGINE, CACHE_ENGINE, INSTANCE_TYPE_FAMILY, BILLING_ENTITY and RESERVATION_ID.

  • group_by_tag_keys: A list of keys used in Cost Explorer to group by tags.