What problem does it solve? Migrating to or operating Amazon Keyspaces (for Apache Cassandra) requires accurate cost estimates, feature-compatibility verification, and safe infrastructure changes, all of which agents frequently get wrong without authoritative guidance. ## Core Features & Use Cases - Pricing Estimation: Calculate monthly on-demand, provisioned, and Savings Plan costs from manual traffic inputs (Mode 1) or from real Cassandra nodetool diagnostics (Mode 2), with optional PDF reports. - Compatibility Checking: Scan CQL schemas and prepared statements to flag unsupported features such as materialized views, secondary indexes, triggers, UDFs, and LWT-in-batch, with migration recommendations (Mode 3). - SQL-to-Keyspaces Migration: Translate relational schemas into three priced NoSQL data-modeling strategies (denormalized, query-driven, wide-row) and recommend one (Mode 4). - Infrastructure Operations: Create keyspaces and tables, configure auto-scaling, CDC, TTL, PITR, encryption, and pre-warming via AWS CLI, with a strict allow/warn/refuse safety model. - Use Case: A team migrating a self-managed Cassandra cluster captures nodetool tablestats and info files, then gets a per-keyspace cost breakdown plus a compatibility report flagging every unsupported feature 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.
