AWS Database Blog
Amazon RDS for MySQL LTS version 9.7 is now generally available
Amazon RDS for MySQL now supports MySQL 9.7, the latest community LTS version, alongside 8.0 and 8.4. This post covers what’s new in 9.7, the key breaking changes, and how to upgrade safely from MySQL 8.4 using Amazon RDS Blue/Green deployments.
Which AWS Database should you use?
Database selection is a foundational decision when building an application. Choosing the right database enables you to focus effort on building customer value while the database scales with demand. AWS offers several fully managed database services. That breadth serves the diversity of the millions of customers who operate databases on AWS, but it raises a practical question: Where do I start? Based on our collective experience working with database customers, this post provides a direct, opinionated answer focused on the job you are trying to perform: migrating an existing workload, refactoring a legacy application, or building something new.
Accelerate your DynamoDB workloads with DynamoDB caching with Amazon ElastiCache Serverless for Valkey
DynamoDB caching with Amazon ElastiCache Serverless for Valkey brings write-through caching to Amazon DynamoDB with sub-millisecond reads and minimal application changes. Serve hot keys from cache, reduce read throttling, and lower read costs while your application keeps calling the DynamoDB API as it does today.
Use query statistics to find slow and expensive queries in Aurora DSQL
When a code change slows your application, Amazon Aurora DSQL query statistics help you find the slow and expensive queries behind it, down to the exact SQL statement. This post walks through a performance investigation that pinpoints a missing index, fixes it with an asynchronous index build, and measures the improvement in latency and DPU cost.
Add your organization’s runbooks and policies using Retrieval Augmented Generation (RAG) on Amazon Aurora PostgreSQL
In Part 2 of this series, you connect your Kiro DBA assistant to your team’s runbooks and policies. Store runbooks in Amazon S3, index them with Amazon Bedrock Knowledge Bases on Amazon Aurora PostgreSQL using pgvector, and wire up retrieval so the assistant grounds its recommendations in your own documentation.
Build an AI-powered DBA assistant for Amazon Aurora and Amazon RDS with Kiro
Learn how to build a DBA assistant with Kiro that investigates and resolves Amazon Aurora PostgreSQL performance incidents through natural language. Using two MCP servers, the agent reads Amazon CloudWatch metrics and Database Insights, runs diagnostic queries, and surfaces fixes you apply through your change management process.
Distribute Amazon RDS traffic between read replicas using Network Load Balancer
Learn how to put Amazon RDS read replicas behind a Network Load Balancer with health-aware, Availability Zone affinity routing. An AWS Lambda function keeps the load balancer target group in sync with replica IP addresses, giving clients a single stable endpoint over Direct Connect or Site-to-Site VPN without AWS PrivateLink overhead.
PostgreSQL large objects: Best practices for Amazon Aurora and RDS
PostgreSQL large objects live outside your tables and are referenced only by an OID, so autovacuum never reclaims the orphans. This post shows how to monitor orphaned large objects on Amazon Aurora and Amazon RDS for PostgreSQL, run vacuumlo safely, set up lo_manage triggers, prevent OID exhaustion, and prepare for major version upgrades.
Exploring new features of Apache TinkerPop 3.8.x in Amazon Neptune
Upgrading to Apache TinkerPop 3.8.x in Amazon Neptune 1.5.0.0 brings cleaner, more predictable Gremlin and a major expansion of Data Flow Engine (DFE) coverage, along with semantic changes that need review. Learn what changed, which query patterns are affected, and how to prepare for the upgrade.
Fix Amazon Aurora MySQL error 63955: Virtual index ID overflow
An Amazon Aurora MySQL cluster can exhaust its virtual index ID limit, after which any CREATE INDEX that includes a virtual column fails with error 63955 until you rebuild the databases. This post shows how to recognize the error, why backups cannot clear it, and how to run a logical dump-and-restore migration with monitoring to catch it next time.









