DynamoDB ConsumedReadCapacity different in CloudWatch and CostExplorer

Hi,

By default cloudWatch metrics for dynamoDB shows ConsumedReadCapacityUnits for a particular table. You can refer this link.

• Units: Count
• Dimensions: TableName, GlobalSecondaryIndexName

In CostExplorer by default, Cost Explorer does not provide a summary of the costs for any one specific table, as it will combine the costs of multiple tables into a total. However, you can use AWS resource tagging to identify each table by a metadata tag. Tags are key-value pairs you can use for a variety of purposes, such as to identify all resources belonging to a project or department. See this link.

Having said above, it might be possible that in cloudwatch, per table metrics is showing and in cost explorer, consumed read capacity units of all tables combined. Please make sure that similar dimensions and statistics are getting used in both cloudwatch and cost explorer.