What problem does it solve? Teams migrating from Apache Cassandra to Amazon Keyspaces often guess at costs, hit unsupported-feature surprises (materialized views, secondary indexes, LWT in batches), and misconfigure drivers, leading to failed connections and throttling. ## Core Features & Use Cases - Cost Estimation: Computes monthly on-demand, provisioned, and Savings Plan pricing from manual traffic inputs (Mode 1) or from real nodetool tablestats/info diagnostics (Mode 2), with optional PDF reports. - Compatibility Checking: Scans CQL schemas and prepared statements to flag UNSUPPORTED features like secondary indexes, triggers, materialized views, UDFs, and LWT-in-unlogged-batch, with migration guidance (Mode 3). - SQL-to-Keyspaces Migration: Translates relational schemas into three priced NoSQL data-modeling strategies (denormalized, query-driven tables, wide rows) for comparison (Mode 4). - Infrastructure Operations & Troubleshooting: Creates keyspaces/tables/UDTs with mandatory tagging, configures TTL, PITR, CDC, auto-scaling, and pre-warming under a strict confirm/warn/refuse safety policy, plus diagnoses connection errors like NoNodeAvailableException and HeartbeatException. - Use Case: A team with a self-managed Cassandra cluster captures diagnostics, runs Mode 2 to get an accurate Keyspaces cost estimate plus a compatibility report, then uses Mode 4 guidance to remodel their SQL-era tables before cutover. ## Quick Start Ask the agent to estimate Amazon Keyspaces costs for your workload by providing your region, reads and writes per second, average row size, and storage in GB.