AWS Database Blog

Today, we announce the Amazon Aurora MySQL power for Kiro. The power connects Kiro’s AI agent to Aurora MySQL and pairs live database access with curated best-practice guidance. You describe what you need in natural language. The agent generates the API calls, SQL, and configuration for you to review and run. In this post, we walk through how the power guides a production migration from Amazon Relational Database Service (Amazon RDS) for MySQL 8.0 to Aurora MySQL through four phases: assessment, replica creation, promotion, and post-cutover validation.

In this post, we show how the integration between Vercel and AWS Databases solves this and invite you to participate in the H0 hackathon.

Amazon receives millions of visits every day, and earning each customer’s trust visit after visit is the foundation that the store is built on. A meaningful part of that trust comes down to whether the recommendations we surface feel relevant and whether they reflect what the customer actually cares about in the moment. In this post, we describe an architecture that makes it achievable. Amazon SageMaker hosts a sentence transformer model on a managed endpoint and turns customer query text into dense semantic vectors. Valkey is an open source, in-memory data store with built-in vector search. It’s available on AWS through Amazon ElastiCache and Amazon MemoryDB. In our architecture, we use Amazon-managed Valkey to store the product catalog as a vector index.

By implementing modern optimization techniques for Aurora, you can achieve additional cost reduction beyond traditional methods alone. This isn’t only about spending less—it’s about building a more efficient, scalable, and resilient database environment. In this post, we show you a structured approach to optimizing Amazon Aurora database costs. It outlines specific strategies, implementation steps, and best practices across different optimization areas.

In this post, we introduce a modular Terraform template, published in the aws-samples/sample-rds-db2-tools repository, that lets your applications keep their existing custom domain names and ports while preserving end-to-end TLS encryption to Amazon RDS for Db2. The template deploys a Server Name Indication (SNI) based TLS proxy that forwards encrypted traffic without ever decrypting it.

Today, we are excited to announce the general availability of Amazon Aurora MySQL 8.4, our latest major version, compatible with community MySQL 8.4.7. This release marks an important milestone for Aurora MySQL customers, introducing a simplified versioning model aligned directly with community MySQL, along with a streamlined patch version experience, and the full set of community MySQL 8.4 enhancements. In this post, we discuss the customer challenges that this release addresses, introduce Aurora MySQL 8.4, walk through the new versioning approach and its benefits for customers, cover the key capabilities delivered in Aurora MySQL 8.4, and show you how to get started.

In this post, we share the version currency timelines for Aurora and RDS open source engines. We also explain why timelines differ across engines and how you can use them to plan your upgrades.

In this post, we show you how to use AWS Fault Injection Service (AWS FIS) to validate that your application handles regional disruptions the way you expect, by running controlled experiments against your DynamoDB global tables. We cover both multi-Region strong consistency (MRSC) and multi-Region eventually consistent (MREC) global tables, because AWS FIS works differently with each.

In this post we cover the two primary failover strategies for DynamoDB global tables, the tradeoffs between them, and the operational considerations that you must be aware of during and after a failover.

This is Part 1 of a series on best practices for DynamoDB global tables. In this post, we focus on preparation: understanding how replication works, what your resilience posture looks like, and the operational groundwork that separates a controlled failover from a scramble.