The only monitoring platform with native ClickHouse support →
Deadline: June 30, 2026

AWS Performance Insights migration guide for RDS and Aurora teams

AWS is moving the Performance Insights experience into CloudWatch Database Insights. If you do nothing, you lose long-window visibility. This page gives you a practical decision path and rollout checklist.

Start Side-by-Side PilotRead Full Background

Decision matrix

Pick the path based on retention needs, pricing constraints, and how locked-in you want to stay.

OptionRetentionPrice modelBest fit
CloudWatch Standard7 daysFreeLow criticality workloads with short investigation windows
CloudWatch AdvancedUp to 24 months~$9/vCPU/month (provisioned)AWS-native teams comfortable with vCPU-based cost growth
Basira side-by-side pilot30 days (today)$29/database/monthTeams that want predictable cost and query-level visibility outside AWS lock-in

CloudWatch Advanced vs Basira cost framing

If your main concern is avoiding visibility loss before June 30, 2026, compare total monitoring spend by instance size before locking in your default.

4 vCPU instance

CloudWatch Advanced$36/mo

Basira$29/mo

16 vCPU instance

CloudWatch Advanced$144/mo

Basira$29/mo

32 vCPU instance

CloudWatch Advanced$288/mo

Basira$29/mo

CloudWatch figure uses the commonly cited ~`$9/vCPU/month` Advanced pricing baseline for provisioned capacity.

Full pricing details: Basira pricing.

Practical migration checklist

  1. 1

    Inventory impacted databases

    List Aurora and RDS instances currently using Performance Insights and map owners.

  2. 2

    Define retention requirements

    For each workload, decide whether 7-day history is acceptable or if you need multi-month investigation windows.

  3. 3

    Model cost at current and projected vCPU

    Estimate CloudWatch Advanced spend and compare with flat per-database alternatives.

  4. 4

    Run a side-by-side pilot

    Keep your current setup while collecting query stats in Basira to validate parity and identify blind spots.

  5. 5

    Finalize default before June 30, 2026

    Set owner, cutoff date, rollback path, and communication plan so migration is explicit, not accidental.

FAQ

Will the Performance Insights API stop working?

No. AWS has indicated the API remains available; the major transition is around the console and pricing model.

What happens if we do nothing before June 30, 2026?

Databases fall back to CloudWatch Standard mode, which has 7-day retention. Longer history is no longer available by default.

Can we evaluate Basira without replacing current monitoring immediately?

Yes. The intended motion is side-by-side pilot first: keep existing alerts, add Basira, compare query-level visibility and cost.

Where do we start the pilot?

Create an account and deploy the agent: app.usebasira.com/signup. Typical setup is minutes, not days.

Run the migration pilot before the deadline

Validate your path now. Keep full query visibility and avoid surprise spend growth.

Start Side-by-Side Pilot