# Amazon DynamoDB Sedai continuously analyzes DynamoDB capacity, GSI usage, and table class fit, then recommends right-sizing, cleanup, and storage changes to make. ## Stop Over-Provisioning DynamoDB Capacity You Don't Use RCUs and WCUs provisioned for peak load sit idle most of the time, and unused GSIs and wrong table classes quietly add to the bill. Sedai analyzes your DynamoDB environment and surfaces the right optimizations to act on. ## DynamoDB Capacity Is Easy to Set, Hard to Right-Size. DynamoDB's managed model removes significant operational burden — but capacity planning still requires ongoing attention. RCU and WCU settings get made for peak load and rarely revisited as usage evolves. Table-level decisions that affect cost — storage class, GSI retention, billing mode — don't optimize themselves. ### Capacity units get set for peak and drift from reality over time. Traffic patterns shift, application usage changes, and the original estimates stop reflecting actual behavior — but revising them requires analysis that competes with higher-visibility engineering work. ### GSIs accumulate long after applications stop querying them. An index created for a feature that was later retired continues generating storage and write costs indefinitely. Auditing GSI usage across a large table inventory is rarely done on a regular cadence. ### Billing mode and storage class decisions rarely get revisited. A table in Provisioned mode might be cheaper in On-Demand as access patterns become spikier. A Standard table might qualify for Standard-IA. These are tractable optimizations — but only if someone is continuously analyzing the data. ## How We Help ### Provisioned Capacity Rightsizing Sedai analyzes historical read and write capacity consumption to identify over-provisioned tables and recommends RCU and WCU adjustments that eliminate waste without compromising performance. ### Unused Index Detection Sedai monitors GSI access patterns and flags indexes with no sustained query activity, surfacing deletion candidates before they continue accumulating storage and throughput costs indefinitely. ### Table Class Optimization Sedai analyzes table access frequency to identify candidates for Standard-IA, recommending the switch where the cost structure better matches actual usage patterns. ## Your DynamoDB Bill Has a Few Things to Say. ## Frequently Asked Questions ### Does Sedai support both provisioned and on-demand capacity modes? Sedai's capacity optimization analysis focuses on provisioned capacity tables, where RCU and WCU allocations are directly controllable. For tables in on-demand mode, Sedai provides visibility into consumption patterns to inform decisions about whether switching to provisioned capacity would reduce costs. ### How does Sedai identify unused GSIs — could it flag an index used only for quarterly reports? Sedai flags GSIs that show no query activity over a sustained monitoring period. We recommend reviewing flagged indexes carefully before deletion — an index that appears idle may still serve infrequent but critical workflows like quarterly reporting. Sedai surfaces the recommendation; your team makes the call. ### Does Sedai apply DynamoDB changes autonomously? Not currently. DynamoDB optimizations are delivered as recommendations rather than autonomous actions. Sedai provides the analysis and identifies the opportunity — execution remains in your hands. ### How does Sedai determine whether Standard-IA is the right table class? Sedai analyzes each table's access frequency against the cost structure of Standard vs. Standard-IA. Standard-IA carries lower storage costs but higher read/write costs, so the recommendation only applies where the access profile makes the tradeoff genuinely favorable. ### Does Sedai support DynamoDB across multiple AWS accounts? Yes. Sedai connects to multi-account AWS environments and provides DynamoDB recommendations consistently across your full account structure.