# AWS Database Blog

Official Database Blog of Amazon Web Services

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Deploy Amazon RDS for Oracle on AWS Outposts

DevFeed: [Deploy Amazon RDS for Oracle on AWS Outposts](<https://devfeed.tech/articles/deploy-amazon-rds-for-oracle-on-aws-outposts-144610.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/deploy-amazon-rds-for-oracle-on-aws-outposts/>)

Author: Vetrivel Subramani

Published: 2026-11-19T22:59:53Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [AWS Outposts](<https://devfeed.tech/topics/aws-outposts.md>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-relational-database-service](<https://devfeed.tech/tags/amazon-relational-database-service.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automated](<https://devfeed.tech/tags/automated.md>), [autoscaling](<https://devfeed.tech/tags/autoscaling.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-management-console](<https://devfeed.tech/tags/aws-management-console.md>), [aws-outposts](<https://devfeed.tech/tags/aws-outposts.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [data-residency](<https://devfeed.tech/tags/data-residency.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [disaster-recovery](<https://devfeed.tech/tags/disaster-recovery.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [on-premises](<https://devfeed.tech/tags/on-premises.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [rds-for-oracle](<https://devfeed.tech/tags/rds-for-oracle.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Amazon RDS for Oracle on AWS Outposts runs managed Oracle databases locally, with automated administration for patching, backups, recovery, and monitoring. The excerpt describes console and CLI deployment: provide an operational Outposts rack, a VPC subnet on the rack, sufficient local capacity, Oracle BYOL licenses, and connectivity to the parent Region; all instances require KMS encryption. It supports Oracle 19c and 26ai, EE and SE2, and rack-specific instance families. Multi-AZ requires two Outposts in different Availability Zones and does not support local backups; read replicas must be on another rack in the same Region. Recovery options include point-in-time restore, replica promotion, and Multi-AZ failover. If Region connectivity is lost, an existing database continues running locally, but instance changes and backups are unavailable until connectivity returns. The excerpt also notes hourly instance management fees, with local storage and backups carrying no separate charge.

### Source excerpt

Learn how to deploy Amazon RDS for Oracle on AWS Outposts to run fully managed Oracle databases on premises while meeting data residency and compliance requirements. This post walks through creating a DB instance using the AWS Management Console and the AWS CLI, and covers disaster recovery options.

## From instant Aurora PostgreSQL databases to production-ready in your VPC

DevFeed: [From instant Aurora PostgreSQL databases to production-ready in your VPC](<https://devfeed.tech/articles/from-instant-aurora-postgresql-databases-to-production-ready-in-your-vpc-144611.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/from-instant-aurora-postgresql-databases-to-production-ready-in-your-vpc/>)

Author: Saurabh Kothawade

Published: 2026-11-19T22:13:11Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [ReAct agent Python](<https://devfeed.tech/topics/react-agent-python.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [console](<https://devfeed.tech/tags/console.md>), [data](<https://devfeed.tech/tags/data.md>), [databases](<https://devfeed.tech/tags/databases.md>), [express](<https://devfeed.tech/tags/express.md>), [iam](<https://devfeed.tech/tags/iam.md>), [networking](<https://devfeed.tech/tags/networking.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [production](<https://devfeed.tech/tags/production.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [verify](<https://devfeed.tech/tags/verify.md>), [vpc](<https://devfeed.tech/tags/vpc.md>)

### AI overview

Aurora PostgreSQL clusters created with express configuration can now move into a VPC through one modify operation, keeping their data and endpoint. The move briefly drops existing connections, switches off the internet access gateway, and requires a prepared DB subnet group, security group, private network path for every client, and suitable IAM permissions. Afterward, verify that the cluster is available with VPC networking enabled and the gateway disabled, then confirm clients reconnect; failed moves can return to gateway access and emit an RDS event. The same operation can be run through the console, AWS CLI, or an AI agent. Agent roles can be scoped to approved clusters and explicitly denied permission to move databases back out of a VPC. Creating directly in a VPC is also supported, though it takes longer than the seconds-long default setup. Moving back to gateway access briefly interrupts connections, requires IAM database authentication, and is blocked while VPC-dependent features are active.

### Source excerpt

Amazon Aurora PostgreSQL express configuration now supports VPC networking. You can move an existing cluster into your VPC with a single modify operation, keeping its data and endpoint, from the console, the AWS CLI, or an AI agent. This post shows how to move and verify a cluster, and how to let an agent do it with IAM guardrails.

## Securing multi-team Amazon Neptune with tag-based access control

DevFeed: [Securing multi-team Amazon Neptune with tag-based access control](<https://devfeed.tech/articles/securing-multi-team-amazon-neptune-with-tag-based-access-control-144313.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/securing-multi-team-amazon-neptune-with-tag-based-access-control/>)

Author: Brian M. Slater

Published: 2026-11-19T21:03:50Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Dynamic authorization rules](<https://devfeed.tech/topics/dynamic-authorization-rules.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [amazon-neptune](<https://devfeed.tech/tags/amazon-neptune.md>), [applications](<https://devfeed.tech/tags/applications.md>), [aws](<https://devfeed.tech/tags/aws.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [data](<https://devfeed.tech/tags/data.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [iam](<https://devfeed.tech/tags/iam.md>), [policies](<https://devfeed.tech/tags/policies.md>), [tag](<https://devfeed.tech/tags/tag.md>), [tags](<https://devfeed.tech/tags/tags.md>), [team](<https://devfeed.tech/tags/team.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Amazon Neptune's tag-based access control (TBAC) can isolate teams on shared clusters by requiring both caller and cluster tags--such as LineOfBusiness and ApplicationID--to match. Separate deny-on-mismatch statements in an organization-level Service Control Policy (SCP) enforce both checks; a central security team can own the guardrail while a provisioning pipeline controls resource tags and federated identity supplies principal tags. The source requires Neptune engine 1.3.x or later and IAM authentication. TBAC gates access at cluster level, not individual graph elements, and connections without IAM authentication bypass these policies. Because a deny-based SCP cannot require IAM authentication at cluster creation, the source recommends provisioning controls, AWS Config detection, and SSM remediation; enabling IAM authentication on an existing cluster restarts its engine and ends open connections. It also notes tag changes take about five minutes to affect evaluation, IAM policy changes up to ten minutes, and suggests validating matched and mismatched access and checking CloudTrail denials. The same tag taxonomy may extend to other data services, subject to each service's condition

### Source excerpt

Amazon Neptune now supports tag-based access control (TBAC) for data-plane operations. This post walks through three scenarios for isolating multiple teams on a shared fleet of Neptune clusters using AWS resource tags and IAM principal tags as conditions in IAM policies and service control policies.

## AWS positioned highest in Ability to Execute in new Gartner Magic Quadrant for Cloud Operational Database Management Systems

DevFeed: [AWS positioned highest in Ability to Execute in new Gartner Magic Quadrant for Cloud Operational Database Management Systems](<https://devfeed.tech/articles/aws-positioned-highest-in-ability-to-execute-in-new-gartner-magic-quadrant-for-cloud-operational-database-management-systems-144310.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/aws-positioned-highest-in-ability-to-execute-in-new-gartner-magic-quadrant-for-cloud-operational-database-management-systems/>)

Author: G2 Krishnamoorthy

Published: 2026-11-19T20:55:23Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [rdbms](<https://devfeed.tech/topics/rdbms.md>), [DSQL](<https://devfeed.tech/topics/dsql.md>), [database-scalability](<https://devfeed.tech/topics/database-scalability.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Managed Services](<https://devfeed.tech/topics/managed-services.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [active-active](<https://devfeed.tech/tags/active-active.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-workflows](<https://devfeed.tech/tags/ai-workflows.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-web-services-aws](<https://devfeed.tech/tags/amazon-web-services-aws.md>), [apache-iceberg](<https://devfeed.tech/tags/apache-iceberg.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [database](<https://devfeed.tech/tags/database.md>), [database-management](<https://devfeed.tech/tags/database-management.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [gartner-magic-quadrant](<https://devfeed.tech/tags/gartner-magic-quadrant.md>), [leader](<https://devfeed.tech/tags/leader.md>), [operational](<https://devfeed.tech/tags/operational.md>), [operational-database](<https://devfeed.tech/tags/operational-database.md>), [thought-leadership](<https://devfeed.tech/tags/thought-leadership.md>)

### AI overview

AWS says Gartner named it a Leader in the Magic Quadrant for Cloud Operational Database Management Systems and placed it highest for Ability to Execute. The excerpt links operational database needs for AI applications to strongly consistent reads, transactions, idempotent writes and durable audit trails. It highlights Aurora for PostgreSQL/MySQL performance and global availability, Aurora DSQL for serverless active-active multi-Region strong consistency, DynamoDB for single-digit-millisecond performance and global tables, and ElastiCache for sub-millisecond caching and auditable requests. AWS also cites MCP connectivity, native vector search, and Aurora PostgreSQL querying Iceberg and Parquet in place. The excerpt promotes the full Gartner report as a resource for understanding its assessment criteria; it does not provide the report's detailed comparisons, and Gartner disclaims endorsing vendors or recommending selection by rating alone.

### Source excerpt

Amazon Web Services (AWS) has been named a Leader in the Gartner Magic Quadrant for Cloud Operational Database Management Systems and is positioned highest of all evaluated vendors for Ability to Execute.

## Performance impact of excessive logging in Amazon Aurora PostgreSQL

DevFeed: [Performance impact of excessive logging in Amazon Aurora PostgreSQL](<https://devfeed.tech/articles/performance-impact-of-excessive-logging-in-amazon-aurora-postgresql-144312.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/performance-impact-of-excessive-logging-in-amazon-aurora-postgresql/>)

Author: Baji Shaik

Published: 2026-11-19T19:10:08Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [bottleneck](<https://devfeed.tech/tags/bottleneck.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [logging](<https://devfeed.tech/tags/logging.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [throughput](<https://devfeed.tech/tags/throughput.md>)

### AI overview

In a pgbench test on Aurora PostgreSQL 17, verbose logging had little effect at 8 clients, but at 800 clients, logging every statement reduced throughput by about 10%; adding `pgaudit.log = ALL` cut whole-run throughput from 16,202 to 5,039 TPS. Sampling showed sessions mostly active on CPU rather than waiting on instrumented resources, and a 537 MB log file written in under a minute supported a bottleneck in log generation and writing. The article recommends checking `pg_settings`, correlating slow periods with `pg_stat_activity` wait events and RDS log-file sizes, and testing at production-like concurrency. For audit needs, it suggests narrowing logged statement classes or using `pgaudit.log_statement = off` to retain structured audit details while dropping embedded SQL text; it advises confirming the reduction on the workload.

### Source excerpt

Excessive database and audit logging can quietly become a performance bottleneck in Amazon Aurora and Amazon RDS for PostgreSQL. Using a reproducible pgbench example, this post shows when logging overhead is negligible and when it cuts throughput by about three times, how to spot it with wait events and log file evidence, and how to reduce it.

## Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache

DevFeed: [Monitor Valkey clusters with OpenTelemetry metrics in Amazon ElastiCache](<https://devfeed.tech/articles/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache-144311.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/monitor-valkey-clusters-with-opentelemetry-metrics-in-amazon-elasticache/>)

Author: Paul Ross

Published: 2026-11-19T18:39:15Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [alarm](<https://devfeed.tech/tags/alarm.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-managed-grafana](<https://devfeed.tech/tags/amazon-managed-grafana.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [insights](<https://devfeed.tech/tags/insights.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [latency](<https://devfeed.tech/tags/latency.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [node](<https://devfeed.tech/tags/node.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [query](<https://devfeed.tech/tags/query.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Amazon ElastiCache for Valkey sends engine and host metrics to CloudWatch in OpenTelemetry format without an exporter or collector. The article demonstrates using ElastiCache Insights to locate a hot shard or node, then PromQL to rank nodes, inspect command latency, and alarm across all nodes as cluster membership changes. Standard monitoring publishes core metrics every 60 seconds; selected detailed metrics arrive every 15 seconds and can expose short latency spikes that a longer window smooths out. Core metrics and ElastiCache Insights are free, while selected detailed metrics, PromQL API scans, and alarms incur charges. The walkthrough requires a node-based Valkey cluster in a supported Region; its Grafana guidance covers version 13 or later, with a separate Prometheus data source approach for version 12.4.

### Source excerpt

Amazon ElastiCache for Valkey now offers OpenTelemetry metrics, detailed monitoring, ElastiCache Insights, and PromQL. This post walks through one troubleshooting path: turn on detailed monitoring, find a hot shard, query with PromQL, catch a short latency spike, and create one alarm that watches every node.

## Amazon ElastiCache Serverless turns three

DevFeed: [Amazon ElastiCache Serverless turns three](<https://devfeed.tech/articles/amazon-elasticache-serverless-turns-three-144309.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/amazon-elasticache-serverless-turns-three/>)

Author: Karthik Konaparthi

Published: 2026-11-19T18:35:55Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [ai-coding-assistant](<https://devfeed.tech/tags/ai-coding-assistant.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [costs](<https://devfeed.tech/tags/costs.md>), [customers](<https://devfeed.tech/tags/customers.md>), [disruption](<https://devfeed.tech/tags/disruption.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [patch](<https://devfeed.tech/tags/patch.md>), [serverless](<https://devfeed.tech/tags/serverless.md>)

### AI overview

Amazon ElastiCache Serverless removes cache capacity planning by scaling with demand; billing is based on stored data (GB-hours) and requests (ECPUs). The article highlights Valkey's faster scaling, lower storage minimum and pricing, plus a 30% Database Savings Plans discount with a one-year commitment. New Valkey 9.0 features include public endpoints (IAM authentication and TLS 1.3 required), online migration from cluster-mode Valkey or Redis OSS with traffic continuing, search, and write-through DynamoDB caching. AWS applies minor and patch updates automatically; major-version upgrades are customer scheduled, and recent patching improvements preserve more connections and in-flight requests. Serverless is presented as a fit for variable traffic and many separate caches; node-based deployments may suit steady workloads, especially with reserved nodes and capacity-tuning staff. The article recommends estimating costs from actual stored data and representative request volume, then checking CloudWatch metrics in a trial workload. Serverless clients must support cluster mode and TLS.

### Source excerpt

In this post, we look back at three years of Amazon ElastiCache Serverless, show how customers use it, cover what we launched this year and how we patch your cache with minimal disruption, show how to estimate what it costs, and help you decide whether it fits your workload.

## Announcing distributed KV caching for self-hosted LLMs with Amazon ElastiCache

DevFeed: [Announcing distributed KV caching for self-hosted LLMs with Amazon ElastiCache](<https://devfeed.tech/articles/announcing-distributed-kv-caching-for-self-hosted-llms-with-amazon-elasticache-142000.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/announcing-distributed-kv-caching-for-self-hosted-llms-with-amazon-elasticache/>)

Author: Meet Bhagdev

Published: 2026-11-18T23:45:25Z

Content type: release

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [valkey](<https://devfeed.tech/topics/valkey.md>), [Self Hosted AI Tools](<https://devfeed.tech/topics/self-hosted-ai-tools.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>), [TensorRT-LLM](<https://devfeed.tech/topics/tensorrt-llm.md>)

Tags: [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [benefits](<https://devfeed.tech/tags/benefits.md>), [caching](<https://devfeed.tech/tags/caching.md>), [costs](<https://devfeed.tech/tags/costs.md>), [distributed-kv](<https://devfeed.tech/tags/distributed-kv.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [general-availability](<https://devfeed.tech/tags/general-availability.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [inference](<https://devfeed.tech/tags/inference.md>), [inference-costs](<https://devfeed.tech/tags/inference-costs.md>), [llm-inference](<https://devfeed.tech/tags/llm-inference.md>), [llm-inference-costs](<https://devfeed.tech/tags/llm-inference-costs.md>), [llms](<https://devfeed.tech/tags/llms.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-hosted-llms](<https://devfeed.tech/tags/self-hosted-llms.md>), [valkey](<https://devfeed.tech/tags/valkey.md>)

### AI overview

Distributed KV caching with Amazon ElastiCache for Valkey adds a shared L2 tier across a GPU fleet, letting vLLM, SGLang, and TensorRT-LLM reuse prompt KV state when local GPU or host caches miss. An open-source LMCache connector requires a configuration change; cache.i8ge.48xlarge nodes use DRAM and NVMe tiering and RDMA over EFA. In tested workloads, gains depended on cache hits and prompt length: shared-document Q&A doubled requests per second and cut cost per million output tokens by 40% while meeting the stated interactivity targets; coding-agent and assistant throughput also increased. Reported TTFT reductions ranged from 55% to 93% across tested models. The post says the least benefit is expected for small deployments with KV state fitting in GPU memory, workloads without prompt reuse, and long outputs from short prompts. It recommends using the free KVTrace tool to estimate hit rate, savings, and cache size before deployment; estimates use hashed prompt data.

### Source excerpt

Today, we are announcing the general availability of distributed KV caching with Amazon ElastiCache for Valkey, a capability that cuts self-hosted LLM inference costs by up to 40% and time to first token by up to 80%. Learn how it works, review benchmark results across workloads and models, deploy it on your own GPU fleet, and size the savings with the open-source KVTrace tool.

## How to use Amazon Aurora DSQL audit logs

DevFeed: [How to use Amazon Aurora DSQL audit logs](<https://devfeed.tech/articles/how-to-use-amazon-aurora-dsql-audit-logs-141385.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-to-use-amazon-aurora-dsql-audit-logs/>)

Author: Koji Shinkubo

Published: 2026-11-18T21:33:01Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Query (disambiguation)](<https://devfeed.tech/topics/query.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-athena](<https://devfeed.tech/tags/amazon-athena.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [athena](<https://devfeed.tech/tags/athena.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audit-logging](<https://devfeed.tech/tags/audit-logging.md>), [audit-logs](<https://devfeed.tech/tags/audit-logs.md>), [configure](<https://devfeed.tech/tags/configure.md>), [database](<https://devfeed.tech/tags/database.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [field](<https://devfeed.tech/tags/field.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [post](<https://devfeed.tech/tags/post.md>), [query](<https://devfeed.tech/tags/query.md>), [records](<https://devfeed.tech/tags/records.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [s3](<https://devfeed.tech/tags/s3.md>), [sql](<https://devfeed.tech/tags/sql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

Aurora DSQL audit logging records configured SQL statement classes and delivers records to S3; it is off until both a destination and recording settings are configured. The article describes role-based scope, including READ/SELECT, and a setup that separates audit administration from DBA permissions. Records can identify the IAM role and database role, transaction, statement, and optionally bound values and row counts. Athena can query the S3 logs, while CloudTrail connection events can be joined by session ID to add client IP information; transaction IDs can also link audit records to CDC changes. Limits and tradeoffs include potentially high log volume and charges, no table- or column-level scope, no client IP or success/failure field in audit records, and recording statements from rolled-back transactions. The article recommends testing scope and volume before production and protecting sensitive log content through access controls, encryption, and retention settings.

### Source excerpt

Amazon Aurora DSQL audit logging records the SQL statements that run in your database and delivers them to Amazon S3. This post shows how to configure audit logging to meet regulatory requirements, explains what each recorded field proves in an audit, and shows how to query the logs in Amazon S3 with Amazon Athena.

## Amazon RDS for MySQL LTS version 9.7 is now generally available

DevFeed: [Amazon RDS for MySQL LTS version 9.7 is now generally available](<https://devfeed.tech/articles/amazon-rds-for-mysql-lts-version-9-7-is-now-generally-available-141384.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/amazon-rds-for-mysql-lts-version-9-7-is-now-generally-available/>)

Author: Sabalesh Mahajan

Published: 2026-11-18T20:52:19Z

Content type: release

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [MySQL](<https://devfeed.tech/topics/mysql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [mysql group replication](<https://devfeed.tech/topics/mysql-group-replication.md>)

Tags: [active-active](<https://devfeed.tech/tags/active-active.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-relational-database-service](<https://devfeed.tech/tags/amazon-relational-database-service.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automation](<https://devfeed.tech/tags/automation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-database-migration-service](<https://devfeed.tech/tags/aws-database-migration-service.md>), [blue-green-deployment](<https://devfeed.tech/tags/blue-green-deployment.md>), [buffer-pool](<https://devfeed.tech/tags/buffer-pool.md>), [bug-fixes](<https://devfeed.tech/tags/bug-fixes.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [cdc-tools](<https://devfeed.tech/tags/cdc-tools.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [checklist](<https://devfeed.tech/tags/checklist.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [lts](<https://devfeed.tech/tags/lts.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-mysql](<https://devfeed.tech/tags/rds-for-mysql.md>)

### AI overview

Amazon RDS for MySQL 9.7 is generally available as the community's latest LTS version. Upgrade from 8.4 directly to 9.7; MySQL 8.0 must first move to 8.4, and 5.7 requires staged upgrades through 8.0 and 8.4. The post recommends Blue/Green deployments to test compatibility before promotion. Before upgrading, address key changes: `rdsproxyadmin` is reserved; `mysql_native_password`, `MD5()` and `SHA1()` are unavailable; TLS is required by default; password validation moves to renamed component settings; and `EXPLAIN` defaults to TREE format. RDS 9.7 uses `gtid_mode=ON_PERMISSIVE`, so outbound replicas must be at least `OFF_PERMISSIVE`. Multi-AZ DB clusters with two readable standbys are unsupported at launch. New capabilities include opt-in Hypergraph optimization, JSON Duality Views and Group Replication components for metrics, flow control, member recovery and primary election.

### Source excerpt

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?

DevFeed: [Which AWS Database should you use?](<https://devfeed.tech/articles/which-aws-database-should-you-use-141386.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/which-aws-database-should-you-use/>)

Author: Joseph Idziorek

Published: 2026-11-18T17:10:51Z

Content type: comparison

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [Amazon DocumentDB](<https://devfeed.tech/topics/amazon-documentdb.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [amazon-com](<https://devfeed.tech/tags/amazon-com.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-neptune](<https://devfeed.tech/tags/amazon-neptune.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [building](<https://devfeed.tech/tags/building.md>), [customer-value](<https://devfeed.tech/tags/customer-value.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [job](<https://devfeed.tech/tags/job.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [legacy-application](<https://devfeed.tech/tags/legacy-application.md>), [managed](<https://devfeed.tech/tags/managed.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>), [selection](<https://devfeed.tech/tags/selection.md>), [thought-leadership](<https://devfeed.tech/tags/thought-leadership.md>)

### AI overview

The article recommends choosing an AWS database by workload: for migrations, use the managed equivalent of the existing database, starting with serverless when possible; for legacy relational refactoring, start with Aurora PostgreSQL serverless, and adopt multiple purpose-built databases only when access patterns or scaling needs warrant it. For new applications, use a database the team already knows; otherwise, start with PostgreSQL, with Aurora PostgreSQL serverless for managed PostgreSQL or Aurora DSQL for relational workloads needing scale and operational simplicity. DynamoDB is suggested for known access patterns and very high throughput, while ElastiCache for Valkey serverless can complement databases for caching. The article points specialized graph, time-series, and document workloads to corresponding services, and names Neptune for connected-data needs in agentic applications. These are opinionated starting points; the article says to match the choice to access patterns, scale, and operational constraints.

### Source excerpt

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

DevFeed: [Accelerate your DynamoDB workloads with DynamoDB caching with Amazon ElastiCache Serverless for Valkey](<https://devfeed.tech/articles/accelerate-your-dynamodb-workloads-with-dynamodb-caching-with-amazon-elasticache-serverless-for-valkey-138649.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/accelerate-your-dynamodb-workloads-with-dynamodb-caching-with-amazon-elasticache-serverless-for-valkey/>)

Author: Varun Gautam

Published: 2026-11-17T23:39:18Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [valkey](<https://devfeed.tech/topics/valkey.md>)

Tags: [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [application](<https://devfeed.tech/tags/application.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [costs](<https://devfeed.tech/tags/costs.md>), [dynamodb](<https://devfeed.tech/tags/dynamodb.md>), [hot-keys](<https://devfeed.tech/tags/hot-keys.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [keys](<https://devfeed.tech/tags/keys.md>), [minimal](<https://devfeed.tech/tags/minimal.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [serve](<https://devfeed.tech/tags/serve.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [valkey](<https://devfeed.tech/tags/valkey.md>), [write](<https://devfeed.tech/tags/write.md>), [write-through](<https://devfeed.tech/tags/write-through.md>)

### AI overview

DynamoDB caching for Amazon ElastiCache Serverless for Valkey routes supported DynamoDB SDK operations through a configured client, serving eventually consistent reads from cache and updating entries after writes reach DynamoDB. Strongly consistent reads bypass the cache and refresh it; unsupported operations and uncached tables go directly to DynamoDB. This can reduce hot-key read pressure and read charges, with sub-millisecond cache responses, while writes still incur DynamoDB costs. Setup requires a new Valkey 9+ serverless cache with DynamoDB caching enabled and IAM authentication, plus client configuration and permissions. The article's example estimates 40-46% lower monthly cost at 20,000 requests per second and a 90% hit rate, but says storage costs can outweigh savings below workload-dependent traffic thresholds; results depend heavily on hit rate and resident data size.

### Source excerpt

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

DevFeed: [Use query statistics to find slow and expensive queries in Aurora DSQL](<https://devfeed.tech/articles/use-query-statistics-to-find-slow-and-expensive-queries-in-aurora-dsql-138653.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/use-query-statistics-to-find-slow-and-expensive-queries-in-aurora-dsql/>)

Author: Rakesh Reddy Kondakindi

Published: 2026-11-17T21:09:25Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [application](<https://devfeed.tech/tags/application.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [build](<https://devfeed.tech/tags/build.md>), [change](<https://devfeed.tech/tags/change.md>), [code](<https://devfeed.tech/tags/code.md>), [cost](<https://devfeed.tech/tags/cost.md>), [dpu](<https://devfeed.tech/tags/dpu.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [help](<https://devfeed.tech/tags/help.md>), [improvement](<https://devfeed.tech/tags/improvement.md>), [index](<https://devfeed.tech/tags/index.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [latency](<https://devfeed.tech/tags/latency.md>), [performance](<https://devfeed.tech/tags/performance.md>), [post](<https://devfeed.tech/tags/post.md>), [queries](<https://devfeed.tech/tags/queries.md>), [query](<https://devfeed.tech/tags/query.md>), [statistics](<https://devfeed.tech/tags/statistics.md>)

### AI overview

Aurora DSQL query statistics record per-statement calls, latency, rows returned and scanned, compute and storage time, and DPU use, complementing sampled DASH metrics. In the walkthrough, CloudWatch Database Insights and Query Studio identify an order-history query scanning about 5.17 million rows to return 20, taking about 12 seconds and 656 DPU per call. EXPLAIN ANALYZE VERBOSE confirms a missing customer_id index. Building an index asynchronously lets the query read matching rows in created_at order and stop after 20; measured latency falls below 3 ms and DPU use to 0.015 per call. Statement statistics must be enabled per cluster and, in multi-Region setups, for each peer cluster. The post's figures come from a reproducible test; its DPU cost example uses US West (Oregon) pricing.

### Source excerpt

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

DevFeed: [Add your organization's runbooks and policies using Retrieval Augmented Generation (RAG) on Amazon Aurora PostgreSQL](<https://devfeed.tech/articles/add-your-organization-s-runbooks-and-policies-using-retrieval-augmented-generation-rag-on-amazon-aurora-postgresql-138650.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/add-your-organizations-runbooks-and-policies-using-retrieval-augmented-generation-rag-on-amazon-aurora-postgresql/>)

Author: Narendra Tawar

Published: 2026-11-17T19:43:40Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Bedrock Knowledge Bases](<https://devfeed.tech/topics/amazon-bedrock-knowledge-bases.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Vectors & LLMs](<https://devfeed.tech/topics/vectors-llms.md>), [Enhancing AI model performance](<https://devfeed.tech/topics/enhancing-ai-model-performance.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-knowledge-bases](<https://devfeed.tech/tags/amazon-bedrock-knowledge-bases.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [pgvector](<https://devfeed.tech/tags/pgvector.md>), [policies](<https://devfeed.tech/tags/policies.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rag](<https://devfeed.tech/tags/rag.md>), [retrieval](<https://devfeed.tech/tags/retrieval.md>), [retrieval-augmented-generation-rag](<https://devfeed.tech/tags/retrieval-augmented-generation-rag.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The walkthrough connects a Kiro DBA assistant to team runbooks and policies using Amazon Bedrock Knowledge Bases, Amazon S3, and Aurora PostgreSQL with pgvector. Bedrock chunks documents, creates Titan Text Embeddings V2 vectors, and stores them with text in Aurora; at query time, the Retrieval MCP server returns relevant chunks for the assistant to ground its recommendations. Setup requires Aurora PostgreSQL 15.4 or later, pgvector, the RDS Data API, and appropriate Bedrock, S3, and Secrets Manager access. The Knowledge Base needs the `mcp-multirag-kb=true` tag for automatic MCP discovery. For structured policies, section-based custom chunking may improve retrieval precision over default chunking. In the example, retrieval surfaces required peer review, CAB approval, and a manual snapshot before schema changes, while suggesting reader-endpoint traffic redirection as an immediate mitigation. The article also stresses that steering files are soft guardrails; read-only database permissions and IAM deny policies provide additional write protection. Re-sync documents as they change, and restrict `bedrock:Retrieve` access to protect sensitive runbooks.

### Source excerpt

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

DevFeed: [Build an AI-powered DBA assistant for Amazon Aurora and Amazon RDS with Kiro](<https://devfeed.tech/articles/build-an-ai-powered-dba-assistant-for-amazon-aurora-and-amazon-rds-with-kiro-138651.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-an-ai-powered-dba-assistant-for-amazon-aurora-and-amazon-rds-with-kiro/>)

Author: Narendra Tawar

Published: 2026-11-17T19:43:17Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [apply](<https://devfeed.tech/tags/apply.md>), [build](<https://devfeed.tech/tags/build.md>), [change](<https://devfeed.tech/tags/change.md>), [change-management](<https://devfeed.tech/tags/change-management.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [database](<https://devfeed.tech/tags/database.md>), [dba](<https://devfeed.tech/tags/dba.md>), [diagnostic](<https://devfeed.tech/tags/diagnostic.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [rds](<https://devfeed.tech/tags/rds.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Kiro can investigate Aurora PostgreSQL performance incidents in one interface by combining two MCP servers: the PostgreSQL server runs diagnostic queries and reads database details, while the CloudWatch server reads metrics, alarms, and logs. Database Insights load, top SQL, and wait events are also retrieved through read-only AWS CLI calls. Setup requires Kiro, Python 3.10+ and uv, AWS credentials with appropriate read permissions, and an Aurora cluster with Database Insights enabled. The assistant is read-only by default and recommends changes for the DBA to review and apply through change management. The article describes three safeguards: steering rules, a PostgreSQL read-only role, and IAM permissions that deny mutations. Its recommendations may need validation because it lacks historical performance data, runbooks, and environment-specific context. The example fix is applied manually after taking a snapshot, then checked with explain plans.

### Source excerpt

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

DevFeed: [Distribute Amazon RDS traffic between read replicas using Network Load Balancer](<https://devfeed.tech/articles/distribute-amazon-rds-traffic-between-read-replicas-using-network-load-balancer-138652.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/distribute-amazon-rds-traffic-between-read-replicas-using-network-load-balancer/>)

Author: Vijay Chakraborty

Published: 2026-11-17T15:51:53Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [read-replica](<https://devfeed.tech/topics/read-replica.md>), [Virtual Private Network](<https://devfeed.tech/topics/vpn.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [connection draining](<https://devfeed.tech/topics/connection-draining.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [affinity](<https://devfeed.tech/tags/affinity.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-container-service](<https://devfeed.tech/tags/amazon-elastic-container-service.md>), [amazon-elastic-kubernetes-service-amazon-eks](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service-amazon-eks.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-route-53](<https://devfeed.tech/tags/amazon-route-53.md>), [amazon-s3](<https://devfeed.tech/tags/amazon-s3.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [aws-privatelink](<https://devfeed.tech/tags/aws-privatelink.md>), [aws-site-to-site-vpn](<https://devfeed.tech/tags/aws-site-to-site-vpn.md>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [health](<https://devfeed.tech/tags/health.md>), [lambda](<https://devfeed.tech/tags/lambda.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [read-replicas](<https://devfeed.tech/tags/read-replicas.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [traffic](<https://devfeed.tech/tags/traffic.md>)

### AI overview

An NLB can provide one stable endpoint for distributing connections across Amazon RDS read replicas, with health checks and Availability Zone affinity. An EventBridge rule invokes a Lambda function every minute to resolve replica DNS names and synchronize their IPs into the NLB target group; S3 JSON state and retry logic help avoid premature deregistration during transient DNS failures. With zonal DNS affinity enabled and cross-zone load balancing disabled, traffic can remain AZ-local in steady state, reducing inter-AZ transfer. The endpoint also supports hybrid access over Direct Connect or Site-to-Site VPN without PrivateLink or Route 53 Resolver endpoints when a custom domain is unnecessary. The approach works with RDS engines that support read replicas, but the NLB balances connections rather than queries, so long-lived connections can limit redistribution. In EKS, CoreDNS placement can undermine zonal affinity; NodeLocal DNSCache is suggested. Deregistration delay allows existing connections to drain.

### Source excerpt

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

DevFeed: [PostgreSQL large objects: Best practices for Amazon Aurora and RDS](<https://devfeed.tech/articles/postgresql-large-objects-best-practices-for-amazon-aurora-and-rds-136897.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/postgresql-large-objects-best-practices-for-amazon-aurora-and-rds/>)

Author: Sachin Murkar

Published: 2026-11-16T23:46:00Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [prevent](<https://devfeed.tech/tags/prevent.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [triggers](<https://devfeed.tech/tags/triggers.md>), [upgrades](<https://devfeed.tech/tags/upgrades.md>)

### AI overview

PostgreSQL large objects can hold values up to 4 TB and support efficient partial reads and updates, but they live outside application tables, so autovacuum does not remove unlinked objects. The article recommends monitoring their count and storage, checking reference columns against vacuumlo's scan criteria, and using dry-run mode before cleanup. vacuumlo recognizes columns named oid or lo, but misses other domains over oid and columns such as integer, bigint, text, or custom types; missed references can be permanently deleted as supposed orphans. lo_manage triggers can unlink objects on row updates or deletes, but do not run for DROP or TRUNCATE. High object counts can also increase OID allocation contention and complicate major upgrades through pg_dump/pg_restore memory use. The guidance includes reducing orphan counts, testing upgrades on a clone, and considering temporary instance scaling when counts remain high.

### Source excerpt

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.

## Fix Amazon Aurora MySQL error 63955: Virtual index ID overflow

DevFeed: [Fix Amazon Aurora MySQL error 63955: Virtual index ID overflow](<https://devfeed.tech/articles/fix-amazon-aurora-mysql-error-63955-virtual-index-id-overflow-133436.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/fix-amazon-aurora-mysql-error-63955-virtual-index-id-overflow/>)

Author: Kartik Saini

Published: 2026-11-13T21:10:28Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [TTL in DNS](<https://devfeed.tech/topics/ttl-in-dns.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [backups](<https://devfeed.tech/tags/backups.md>), [dump](<https://devfeed.tech/tags/dump.md>), [error](<https://devfeed.tech/tags/error.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [index](<https://devfeed.tech/tags/index.md>), [limit](<https://devfeed.tech/tags/limit.md>), [logical](<https://devfeed.tech/tags/logical.md>), [migration](<https://devfeed.tech/tags/migration.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [rebuild](<https://devfeed.tech/tags/rebuild.md>), [restore](<https://devfeed.tech/tags/restore.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [virtual](<https://devfeed.tech/tags/virtual.md>)

### AI overview

Aurora MySQL error 63955 means the cluster has exhausted virtual index IDs: indexes containing virtual columns--including functional and multi-valued indexes--fail, while existing data and ordinary indexes remain usable. Changing a generated column to STORED can unblock that particular index, but does not reset the IDs. The documented fix is a logical dump and restore; snapshots, clones, point-in-time recovery, and Blue/Green deployments copy physical structures and do not clear the condition. The described migration uses a clone, binary log replication, MyDumper/MyLoader, and a new Aurora MySQL 3.10.0-or-later cluster. It requires planning for a source reboot to enable binary logging, preserving the clone's source log position, migrating users and grants separately, validating the restore, and limiting rollback because schema changes can break reverse replication. On 3.10.0 or later, monitor the error log for VIRTUAL_INDEX_ID_OVERFLOW_WARNING; it is the only stated advance signal.

### Source excerpt

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.

## Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 1: Common causes](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes-133437.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-1-common-causes/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:09Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [fragmentation](<https://devfeed.tech/tags/fragmentation.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [pool](<https://devfeed.tech/tags/pool.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [transactions](<https://devfeed.tech/tags/transactions.md>)

### AI overview

RDS Proxy multiplexing for PostgreSQL is reduced when sessions are pinned, client identities fragment the pool, or transactions remain open. CloudWatch indicators help distinguish them: elevated session-pinned connections suggest pinning; many backend connections with low borrowing and pinning can indicate fragmentation; sustained borrowing and open transactions point to transactions held too long. Fixes include upgrading the PostgreSQL JDBC driver to 42.7.x or newer, removing application SET statements, setting Spark JDBC writes to isolationLevel=NONE, and using InitQuery for shared session defaults. Standardize username, database, and ApplicationName among clients that should share a pool, while preserving separate users when privilege or audit needs require them. Commit promptly or enable autocommit where explicit transaction control is unnecessary. PostgreSQL targets do not support the proxy's SET pinning filter, and CloudWatch gauges can miss short-lived borrow cycles.

### Source excerpt

RDS Proxy multiplexes many client connections across a small pool of database connections, but connection pinning, pool fragmentation, and uncommitted transactions can silently disable that benefit for PostgreSQL workloads. Part 1 shows how to recognize each condition with Amazon CloudWatch metrics and the fix that restores multiplexing.

## Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor

DevFeed: [Improve RDS Proxy multiplexing for PostgreSQL, Part 2: Diagnose and monitor](<https://devfeed.tech/articles/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor-133438.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/improve-rds-proxy-multiplexing-for-postgresql-part-2-diagnose-and-monitor/>)

Author: Pavel Rabinovich

Published: 2026-11-13T21:08:04Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon CloudWatch Logs](<https://devfeed.tech/topics/amazon-cloudwatch-logs.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-cloudwatch-logs](<https://devfeed.tech/tags/amazon-cloudwatch-logs.md>), [amazon-emr](<https://devfeed.tech/tags/amazon-emr.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [insights](<https://devfeed.tech/tags/insights.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [regression](<https://devfeed.tech/tags/regression.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

CloudWatch metrics can show that RDS Proxy multiplexing has degraded, but enhanced proxy logs help explain why and which connections are involved. CloudWatch Logs Insights queries summarize backend connection borrows, releases, and pins, or trace one connection's lifecycle. For user and ApplicationName attribution, the post correlates proxy TCP events with PostgreSQL connection logs using IP:port; this is a best-effort match that depends on a narrow time window and synchronized timestamps. Healthy multiplexing shows many borrows and releases per backend connection, few pins, and substantially fewer backend than client connections. The post recommends alarms for sustained pinning and an elevated backend-to-client connection ratio, with workload-specific baselines and a traffic floor. Enhanced logging produces detailed SQL text, adds log volume, cost, and possible proxy overhead, so restrict log access, use it temporarily, and disable it after diagnosis.

### Source excerpt

Metrics alone can't always pinpoint what is reducing RDS Proxy multiplexing for PostgreSQL. Part 2 shows how to use Amazon CloudWatch Logs Insights with enhanced proxy logs to find the root cause, what healthy multiplexing looks like in metrics and logs, and how to set up CloudWatch alarms that catch regression.

## Boosting Amazon RDS for PostgreSQL with AWS Graviton5: Benchmarks

DevFeed: [Boosting Amazon RDS for PostgreSQL with AWS Graviton5: Benchmarks](<https://devfeed.tech/articles/boosting-amazon-rds-for-postgresql-with-aws-graviton5-benchmarks-131172.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/boosting-amazon-rds-with-aws-graviton5-benchmarks/>)

Author: Angel Duenas

Published: 2026-11-12T23:59:59Z

Content type: comparison

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Graviton](<https://devfeed.tech/topics/graviton.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [AWS CloudFormation](<https://devfeed.tech/topics/aws-cloudformation.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudformation](<https://devfeed.tech/tags/aws-cloudformation.md>), [aws-graviton](<https://devfeed.tech/tags/aws-graviton.md>), [aws-secrets-manager](<https://devfeed.tech/tags/aws-secrets-manager.md>), [aws-systems-manager](<https://devfeed.tech/tags/aws-systems-manager.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [graviton5](<https://devfeed.tech/tags/graviton5.md>), [m9g](<https://devfeed.tech/tags/m9g.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [rds](<https://devfeed.tech/tags/rds.md>), [rds-for-postgresql](<https://devfeed.tech/tags/rds-for-postgresql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [throughput](<https://devfeed.tech/tags/throughput.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

In this Sysbench OLTP read/write benchmark, Graviton5-based M9g delivered the highest throughput among Amazon RDS for PostgreSQL instance generations M6g through M9g, with 55% lower p95 latency than M6g, 92% more queries per dollar than M6g, and 20% more than M8g. Tests used PostgreSQL 17.10, default RDS parameters apart from enforced TLS, io2 storage, a 100-thread workload, and five 30-minute runs per class; reported results are medians. The setup aimed to isolate CPU-generation effects, so gains may differ for workloads with another CPU, memory, and I/O balance. The article says Multi-AZ class changes use automatic failover with minimal downtime, while its tested Single-AZ setup needs a brief reboot, and recommends testing production workloads before upgrading.

### Source excerpt

AWS Graviton5 is now available on Amazon RDS through the new M9g instance family. In this post, we benchmark M9g against the M6g, M7g, and M8g generations for Amazon RDS for PostgreSQL, measuring throughput, latency, and price-performance so you can decide whether an upgrade is worth it.

## Using AWS Backup to resynchronize a SQL Server AlwaysOn Availability Group

DevFeed: [Using AWS Backup to resynchronize a SQL Server AlwaysOn Availability Group](<https://devfeed.tech/articles/using-aws-backup-to-resynchronize-a-sql-server-alwayson-availability-group-131175.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/using-aws-backup-to-resynchronize-a-sql-server-alwayson-availability-group/>)

Author: Gabriel Pereira

Published: 2026-11-12T18:37:14Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [sql-server](<https://devfeed.tech/topics/sql-server.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon Elastic Block Store (Amazon EBS)](<https://devfeed.tech/topics/amazon-elastic-block-store-amazon-ebs.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [alwayson](<https://devfeed.tech/tags/alwayson.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [amazon-elastic-block-store-amazon-ebs](<https://devfeed.tech/tags/amazon-elastic-block-store-amazon-ebs.md>), [amazon-elastic-compute-cloud-amazon-ec2](<https://devfeed.tech/tags/amazon-elastic-compute-cloud-amazon-ec2.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-backup](<https://devfeed.tech/tags/aws-backup.md>), [backup](<https://devfeed.tech/tags/backup.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [rebuild](<https://devfeed.tech/tags/rebuild.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [replica](<https://devfeed.tech/tags/replica.md>), [restore](<https://devfeed.tech/tags/restore.md>), [snapshot](<https://devfeed.tech/tags/snapshot.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS Backup can rebuild a failed SQL Server AlwaysOn secondary by restoring an application-consistent, VSS-enabled EC2 snapshot, then reconfiguring the node and rejoining it to the Availability Group. This EC2-level restore avoids streaming data from the primary as automatic seeding does and avoids the manual full backup, shipping, and restore cycle. The SQL Server VSS restore runbook cannot restore a secondary; it is limited to standalone databases or AG primaries. After restore, secondary IP addresses must be assigned manually. If VSS prerequisites are missing, resolve any cluster split-brain before rejoining. A broken LSN chain--such as when a primary log backup truncates records while the secondary is offline--requires per-database differential and log backups restored on the secondary with NORECOVERY before rejoining. The text reports about 10 minutes for one 100 GB lab restore and 6m13s to copy backup files in its broken-chain scenario; actual timing depends on volume size, file size, network throughput, and storage performance.

### Source excerpt

Learn how to use AWS Backup to rebuild a failed secondary replica in a SQL Server AlwaysOn Availability Group on Amazon EC2. We walk through capturing an application-consistent snapshot, restoring the EC2 instance, rejoining the Availability Group, and handling a broken LSN chain to reduce recovery time compared to a manual backup and restore.

## AI-driven database investigation using MCP, Agent Skills, and AWS DevOps Agent

DevFeed: [AI-driven database investigation using MCP, Agent Skills, and AWS DevOps Agent](<https://devfeed.tech/articles/ai-driven-database-investigation-using-mcp-agent-skills-and-aws-devops-agent-131174.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/integrate-mcp-tools-agent-skills-and-aws-devops-agent-for-ai-driven-database-investigation/>)

Author: Sudhir Amin

Published: 2026-11-12T18:34:07Z

Content type: article

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>), [RDS for SQL Server](<https://devfeed.tech/topics/rds-for-sql-server.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-skills](<https://devfeed.tech/tags/agent-skills.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [connect](<https://devfeed.tech/tags/connect.md>), [database](<https://devfeed.tech/tags/database.md>), [dba](<https://devfeed.tech/tags/dba.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devops-agent](<https://devfeed.tech/tags/devops-agent.md>), [diagnostic](<https://devfeed.tech/tags/diagnostic.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [rds-for-sql-server](<https://devfeed.tech/tags/rds-for-sql-server.md>), [skills](<https://devfeed.tech/tags/skills.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

AWS DevOps Agent can investigate RDS for SQL Server incidents by combining CloudWatch and Database Insights telemetry with SQL-specific MCP tools hosted in Lambda and exposed through Amazon Bedrock AgentCore Gateway. A Markdown skill defines triage thresholds, diagnostic steps, and report format; built-in telemetry identifies the problem type, while Gateway tools retrieve session, query, plan, and index details. In the example, an alarm led the agent to identify a head blocker holding a lock on dbo.Orders, with about 14 sessions waiting. It linked recurring spikes to a five-minute transaction pattern, noted it could not identify the client process, and recommended removing the delay, bounding client timeouts, and raising the alarm threshold. Access is constrained through SigV4, an allowlist, Secrets Manager credential retrieval by Lambda, and a read-only SQL login. The sample requires Database Insights, suitable database permissions, private VPC access, and supported AWS services and region.

### Source excerpt

Learn how to connect Amazon RDS for SQL Server diagnostic tools to AWS DevOps Agent through Amazon Bedrock AgentCore Gateway. MCP tools run in AWS Lambda behind a governed Gateway endpoint, and an investigation skill encodes your DBA team's method so the agent can triage alarms and run autonomous, auditable database investigations.

## Build a serverless recipe-sharing API with Go and Amazon Aurora DSQL

DevFeed: [Build a serverless recipe-sharing API with Go and Amazon Aurora DSQL](<https://devfeed.tech/articles/build-a-serverless-recipe-sharing-api-with-go-and-amazon-aurora-dsql-131173.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-a-serverless-recipe-sharing-api-with-go-and-amazon-aurora-dsql/>)

Author: Steve Brown

Published: 2026-11-12T16:14:20Z

Content type: tutorial

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [DSQL](<https://devfeed.tech/topics/dsql.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Erlang](<https://devfeed.tech/topics/erlang.md>)

Tags: [amazon-api-gateway](<https://devfeed.tech/tags/amazon-api-gateway.md>), [amazon-aurora](<https://devfeed.tech/tags/amazon-aurora.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloudformation](<https://devfeed.tech/tags/cloudformation.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [dsql](<https://devfeed.tech/tags/dsql.md>), [go](<https://devfeed.tech/tags/go.md>), [iam](<https://devfeed.tech/tags/iam.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [keys](<https://devfeed.tech/tags/keys.md>), [optimistic-concurrency](<https://devfeed.tech/tags/optimistic-concurrency.md>), [recipe](<https://devfeed.tech/tags/recipe.md>), [referential-integrity](<https://devfeed.tech/tags/referential-integrity.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>), [retries](<https://devfeed.tech/tags/retries.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [token](<https://devfeed.tech/tags/token.md>), [uuid](<https://devfeed.tech/tags/uuid.md>)

### AI overview

The article demonstrates a Go recipe-sharing REST API that runs locally as a Gin HTTP server or on AWS Lambda behind API Gateway, using the same handlers and an Amazon Aurora DSQL store. It describes UUID text primary keys to spread writes across storage partitions; short-lived IAM tokens, TLS, and a pgx connection pool managed by the Go connector; and separate DDL operations because DDL and DML cannot share a transaction. The sample checks chef and recipe references in handlers, though the database can enforce them with foreign keys instead. Aurora DSQL optimistic concurrency conflicts can be retried by the connector's occretry package with exponential backoff, so transaction logic should be idempotent. Deployment uses a script and CloudFormation for Lambda, API Gateway, IAM, and logs; its IP allowlist is not authentication, and the article recommends adding an authorization method for production. The text also notes connection recycling before the 60-minute server limit and low pool sizing for single-request Lambda invocations.

### Source excerpt

Build a fully serverless recipe-sharing REST API in Go on Amazon Aurora DSQL, AWS Lambda, and Amazon API Gateway. Learn UUID primary keys for even write distribution, short-lived IAM token authentication, application-layer referential integrity, and automatic optimistic-concurrency retries, with a one-command CloudFormation deployment.

[Next page](<https://devfeed.tech/sources/aws-database-blog.md?cursor=WyIyMDI2LTExLTEyVDE2OjE0OjIwKzAwOjAwIiwgIjc0YzE5NzYzLWFlOWYtNDNkYy1hYWIwLTUyMDQyZjkxNmNhZiJd>)