DynamoDB Contributor Insights Pricing: What You're Actually Paying For

DynamoDB Contributor Insights pricing consists of a fixed rule fee of $0.50 per rule per month (with one table auto-creating four rules, resulting in a $2.00 monthly minimum) and a variable event fee of $0.03 per million events. As of August 2025, AWS introduced a throttle-only mode that significantly reduces event costs by only charging for events that result in throttling, making the feature highly cost-effective for identifying hot keys that waste provisioned capacity.

/$0.50 per rule per month. $0.03 per million events. Enabling Contributor Insights on a single DynamoDB table auto-creates four rules so your floor is $2.00/month before a single event is counted. At 500 million events/month, that's $17.00/month. At 5 billion, it's $152.00/month. Whether that's justified depends on your traffic volume, whether you have hot key patterns, and what throttling is already costing you in wasted provisioned throughput. Contributor Insights for DynamoDB is a CloudWatch monitoring feature that identifies the top partition keys driving read and write traffic on a table without any code-level instrumentation or custom application logging. It analyzes request traffic in near real-time and publishes results as CloudWatch graphs. For tables with partition key skew, it answers the specific question a FinOps engineer needs: "Which partition key is causing throttling?" The Two Pricing Components Contributor Insights billing has exactly two line items on your CloudWatch invoice: How many rules does one table create? Enabling on a single table auto-creates four rules: Rule count formula: 2 + 2 × number of GSIs A table with no GSIs = $2.00/month in rule fees. A table with 3 GSIs = $4.00/month in rule fees, before any events. What counts as an "event"? Every read and write operation: GetItem, PutItem, UpdateItem, DeleteItem, BatchGetItem, BatchWriteItem each item individually , Query and Scan each item returned or examined , and transactional reads/writes. GSI operations are counted separately when rules are active on both. 10M events/month: $2.00 rule fee + $0.30 event fee = $2.30/month 500M events/month: $2.00 rule fee + $15.00 event fee = $17.00/month 2B events/month: $2.00 rule fee + $60.00 event fee = $62.00/month 2B events/month + 3 GSIs: $4.00 rule fee + $60.00 event fee = $64.00/month For most workloads, the event fee is the variable that matters. The rule fee is fixed overhead. As of August 2025, AWS added a throttle-only mode. Rules only activate for events that result in throttling requests that exceed provisioned capacity or on-demand burst limits. You still pay the $0.50/rule/month rule fee. But the event fee drops dramatically. On a well-provisioned table with a 0.1% throttle rate processing 2 billion events/month, you'd match roughly 2 million throttled events, an event cost of $0.06/month instead of $60.00/month. Use throttle-only mode when: Use full mode when: If you're deciding between 1-year and 3-year AWS commitment terms before locking in Reserved Capacity, the tradeoffs are covered in detail here How to Choose Between 1-Year and 3-Year AWS Commitments Contributor Insights costs $2 to $62/month. The cost of not having it shows up in your provisioned capacity bill every month. DynamoDB provisioned capacity is distributed across partitions. If your table is configured for 10,000 RCUs/second and 90% of reads go to three partition keys, the capacity on your other partitions sits idle while those three keys throttle. Common patterns where this happens: A concrete scenario: a table provisioned at 5,000 WCUs/second costs approximately $2,847/month in write capacity verify current rates at aws.amazon.com/dynamodb/pricing . If hot key throttling means 30% of that capacity is sitting idle on underutilized partitions, you're paying ~$854/month for throughput you can't use. Contributor Insights at $17/month to identify which keys to redesign around: that's a 50:1 return in the month you act on it. Hot Keys and Reserved Capacity Commitments This is where hot key detection connects directly to cost optimization strategy. DynamoDB Reserved Capacity delivers 30–40% savings on provisioned throughput. But those savings assume your capacity is being utilized effectively. A table with undetected hot key patterns has two compounding problems: The right sequence: identify hot keys via Contributor Insights → fix the partition key schema → right-size provisioned capacity → apply Reserved Capacity on that right-sized number. The result is a smaller commitment with higher utilization and 30–40% off the correct baseline. CloudWatch already provides DynamoDB metrics by default, at no charge. The key difference is specificity. Standard CloudWatch metrics tell you "you have 50,000 throttled requests this hour." Contributor Insights tells you "partition key user 12345 accounts for 48,000 of those throttled requests." For active troubleshooting or capacity planning, that distinction is the difference between guessing and acting. Enable Contributor Insights when: Use throttle-only mode when: Skip it entirely when: Prerequisites: IAM permissions for cloudwatch:EnableInsightRules and dynamodb:DescribeTable. Understand the event cost for your traffic volume before enabling full mode. If rules show an "Error" state, the most common cause is insufficient IAM permissions. Verify the execution role includes cloudwatch:EnableInsightRules, cloudwatch:PutInsightRule, and dynamodb:DescribeTable. Identifying hot keys is a prerequisite to maximizing Reserved Capacity ROI. A table with hot key throttling shows a deceptive utilization signal: total consumed capacity may look high, but actual table-level efficiency is low because hot partitions throttle while cold partitions sit idle. Usage.ai's Flex Reserved Instances handle DynamoDB Reserved Capacity commitments with no upfront payment, no multi-year lock-in, and a cashback guarantee if utilization falls short see how it works at usage.ai Usage.ai refreshes DynamoDB recommendations every 24 hours, vs. the 72+ hour refresh cycle on AWS native tools. At DynamoDB pricing, that 3-day gap in detecting newly-emerged hot key patterns can represent meaningful daily waste before any action is taken. Have you run into hot key issues on DynamoDB? Did you catch it via Contributor Insights or some other way and what did the fix end up looking like? Explore the full operational breakdown here → DynamoDB Contributor Insights Pricing: Monitoring Hot Keys at a Cost