# Amazon RDS

Sedai continuously analyzes Amazon RDS and autonomously rightsizes instances through maintenance windows — safe enough for production databases.

## RDS Rightsizing That's Actually Safe to Act On

Most teams avoid resizing production databases — the risk feels too high and the analysis too complex. Sedai continuously analyzes your RDS fleet and applies instance rightsizing changes autonomously, using maintenance windows and incremental adjustments to keep risk minimal.

Sedai is an autonomous cloud optimization platform that continuously analyzes Amazon RDS fleets and autonomously rightsizes instances, optimizes storage configurations, and identifies unused resources. Unlike recommendation-only tools, Sedai applies changes through maintenance windows with incremental adjustments — making it safe enough for production databases. It supports RDS, Aurora, Multi-AZ deployments, and multi-account environments.

## Nobody Touches a Production Database That's Working.

RDS handles the operational overhead of running a managed database, but the resource decisions that drive cost and performance still belong to your team. Instance sizing, storage configuration, and replica strategy are all difficult to revisit safely once a database is carrying real production traffic.

### Instances get provisioned for peak load and stay there.

Rightsizing a production database means accepting regression risk on a system with high blast radius and slow recovery. Most teams make the rational choice to leave it alone — and pay for unused headroom indefinitely.

### Storage configuration involves tradeoffs that aren't obvious at provisioning time.

Allocated storage can grow but can’t shrink in place, so every overestimate becomes permanent spend. Volume type and provisioned IOPS add tradeoffs, and getting them wrong means overpaying for throughput or hitting I/O limits.

### Idle infrastructure compounds quietly in the background.

Dev and staging instances running outside business hours, read replicas with minimal traffic, databases for deprioritized projects — these accumulate across accounts without triggering alerts. The cost shows up in the bill; the cause rarely surfaces without a dedicated audit.

## How We Help

### Instance Rightsizing

Sedai analyzes utilization at the 95th percentile to identify the optimal instance type and applies changes autonomously during scheduled maintenance windows to minimize production risk.

### Storage Optimization

Sedai evaluates volume type, provisioned IOPS, and throughput against actual usage, and recommends the storage configuration that meets performance requirements at the lowest cost. That includes gp2-to-gp3 migrations and trimming over-provisioned IOPS.

### Unused Resource Cleanup

Sedai identifies inactive RDS instances and read replicas with no traffic, flagging them for decommissioning before they quietly accumulate months of unnecessary spend.

## Sedai vs AWS Compute Optimizer

| AWS Compute Optimizer | Sedai |
| --- | --- |
| Recommends instance changes; you execute manually | Analyzes, decides, and applies changes autonomously through maintenance windows |
| Analyzes CPU and memory only; no storage or IOPS optimization | Optimizes instance type, storage configuration, and provisioned IOPS together |
| Point-in-time recommendations that go stale as workloads shift | Continuous analysis with 95th-percentile modeling that adapts to traffic changes |
| No awareness of maintenance windows or deployment topology | Schedules changes during maintenance windows; handles Multi-AZ failover timing |
| No action on idle resources | Identifies inactive instances and read replicas with cost impact and connection history |

## Production Databases Deserve Better Than Manual Guesswork.

## Frequently Asked Questions

### How does Sedai avoid causing performance issues when rightsizing a production database?

Sedai analyzes utilization at the 95th percentile rather than average usage, ensuring recommendations preserve enough headroom for peak load. Changes are applied incrementally and scheduled during maintenance windows by default, minimizing the risk of impacting live traffic.

### Does Sedai support both standard RDS and Aurora?

Yes. Sedai supports both RDS and Aurora deployments, including storage-specific optimizations for Aurora such as recommendations between Standard and I/O-Optimized storage configurations.

### How does Sedai handle Multi-AZ deployments?

Sedai's rightsizing analysis accounts for Multi-AZ configurations. Instance type changes in Multi-AZ deployments involve a failover event, which Sedai schedules during the maintenance window to minimize disruption.

### Will Sedai delete unused RDS instances automatically?

No. Decommissioning recommendations for inactive instances and read replicas require explicit approval. Sedai surfaces the opportunity with supporting context — connection history, cost impact — but deletion stays in human hands.

### Does Sedai support RDS across multiple AWS accounts and regions?

Yes. Sedai analyzes and optimizes RDS deployments across multi-account and multi-region AWS environments, with consistent rightsizing and storage optimization applied across your full fleet.