What problem does it solve? Migrating to or operating Amazon Keyspaces (for Apache Cassandra) requires accurate cost estimates, authoritative answers on which Cassandra features are unsupported, and safe execution of infrastructure changes — all areas where agents frequently produce incomplete or incorrect answers without grounded guidance. ## Core Features & Use Cases - Pricing Estimation: Calculate monthly costs from manual traffic inputs (Mode 1) or from real Cassandra nodetool diagnostics (Mode 2), comparing on-demand, provisioned, and Savings Plan totals. - Compatibility Checking: Scan CQL schemas and prepared statements to flag unsupported features — materialized views, secondary indexes, triggers, UDFs, UDAs, and LWT inside unlogged batches — with migration recommendations. - SQL-to-Keyspaces Migration: Translate relational schemas into three priced data-modeling strategies (denormalized, query-driven tables, wide rows with clustering keys). - Infrastructure Operations: Create keyspaces and tables, configure auto-scaling, CDC, TTL, PITR, encryption, and pre-warming via AWS CLI, with a strict confirm/warn/refuse safety policy. - Use Case: A team migrating a self-managed Cassandra cluster captures nodetool tablestats and info files, runs the diagnostics workflow, and receives a per-keyspace cost breakdown plus a compatibility report flagging their materialized views before cutover. ## Quick Start Ask the assistant to estimate Amazon Keyspaces costs for a workload with a given region, reads per second, writes per second, row size, and storage, or to check whether your Cassandra schema is compatible with Keyspaces.
