# Amazon RDS

Amazon Relational Database Service (Amazon RDS) is a managed relational database service that automates tasks such as provisioning, configuring, backing up, and patching.

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.

## 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.

## 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.

## 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.

## Introducing AWS Backup logically air-gapped vault support for Amazon RDS

DevFeed: [Introducing AWS Backup logically air-gapped vault support for Amazon RDS](<https://devfeed.tech/articles/introducing-aws-backup-logically-air-gapped-vault-support-for-amazon-rds-137222.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/storage/introducing-aws-backup-logically-air-gapped-vault-support-for-amazon-rds/>)

Author: Mounika Buragapu

Published: 2026-11-16T19:19:22Z

Content type: release

Language: en

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

Topics: [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [backups](<https://devfeed.tech/topics/backups.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>), [AWS IAM Identity Center](<https://devfeed.tech/topics/aws-iam-identity-center.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [air-gapped](<https://devfeed.tech/tags/air-gapped.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [aws-backup](<https://devfeed.tech/tags/aws-backup.md>), [backup](<https://devfeed.tech/tags/backup.md>), [backups](<https://devfeed.tech/tags/backups.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cyber-recovery](<https://devfeed.tech/tags/cyber-recovery.md>), [database](<https://devfeed.tech/tags/database.md>), [design](<https://devfeed.tech/tags/design.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [recovery](<https://devfeed.tech/tags/recovery.md>), [strategy](<https://devfeed.tech/tags/strategy.md>), [vault](<https://devfeed.tech/tags/vault.md>)

### AI overview

AWS Backup can store Amazon RDS snapshots in logically air-gapped vaults held in a service-owned account and automatically locked in compliance mode. In this excerpt, copying is limited to the same account and Region; continuous backups with point-in-time recovery stay in a standard vault, so snapshot frequency determines the air-gapped copy's recovery point objective. AWS RAM enables direct restores and scheduled restore testing from a separate account, while Multi-party approval provides controlled access if the owning account or Organization is compromised. RDS instances encrypted with the AWS managed aws/rds key cannot be copied to these vaults; they need a customer managed key or no encryption. Air-gapped storage costs more: primary-target workflows also incur temporary standard-vault storage, while copy actions retain and charge for recovery points in both vaults. The excerpt also describes a separate standard-vault copy in another Region for regional recovery.

### Source excerpt

AWS Backup now extends logically air-gapped vault support to Amazon RDS. Learn how to protect, validate, and recover your RDS database backups with isolated, immutable vaults, along with the design, encryption, and cost considerations for a cyber recovery strategy that keeps backups recoverable even when your production account can't be trusted.

## 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.

## Building a self-service LLM gateway with Amazon Bedrock and LiteLLM

DevFeed: [Building a self-service LLM gateway with Amazon Bedrock and LiteLLM](<https://devfeed.tech/articles/building-a-self-service-llm-gateway-with-amazon-bedrock-and-litellm-130770.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/building-a-self-service-llm-gateway-with-amazon-bedrock-and-litellm/>)

Author: Sitaraman Vijay Krishna

Published: 2026-11-12T18:41:12Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [litellm](<https://devfeed.tech/topics/litellm.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [self-service](<https://devfeed.tech/topics/self-service.md>), [internal developer portal](<https://devfeed.tech/topics/internal-developer-portal.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-fargate](<https://devfeed.tech/tags/aws-fargate.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [controls](<https://devfeed.tech/tags/controls.md>), [cost](<https://devfeed.tech/tags/cost.md>), [developers](<https://devfeed.tech/tags/developers.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [litellm](<https://devfeed.tech/tags/litellm.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-gateway](<https://devfeed.tech/tags/llm-gateway.md>), [self-service](<https://devfeed.tech/tags/self-service.md>), [service](<https://devfeed.tech/tags/service.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The article presents a self-service LLM gateway pattern that puts Amazon Bedrock behind LiteLLM's OpenAI-compatible API on AWS Fargate. Developers use a single base URL and per-user keys; LiteLLM manages key budgets and rate limits, PostgreSQL stores key and spend state, Valkey provides caching and distributed rate limiting, and Bedrock inference profiles provide model-level quota isolation and routing. Langfuse captures prompt-level traces while CloudWatch tracks operational metrics; prompt logging requires suitable redaction, retention, and access controls. Key implementation requirements include LiteLLM Enterprise for SSO-based self-service key issuance, explicit per-model token pricing for budget enforcement, PostgreSQL for persistent state, and IAM permissions for both inference-profile and underlying model resources. The authors recommend long request timeouts for extended thinking, retrying throttled requests on the same model, and separating automation traffic. The post offers illustrative snippets rather than a complete deployable stack, and its examples use Claude models.

### Source excerpt

Build a self-service LLM gateway with LiteLLM on AWS Fargate that puts Amazon Bedrock foundation models behind an OpenAI-compatible API. Developers get instant access through a single API key, while platform teams gain per-user cost controls, quota isolation, and observability.

## Resilient IAM database authentication with Amazon Aurora Global Database writer endpoint

DevFeed: [Resilient IAM database authentication with Amazon Aurora Global Database writer endpoint](<https://devfeed.tech/articles/resilient-iam-database-authentication-with-amazon-aurora-global-database-writer-endpoint-129590.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/resilient-iam-database-authentication-with-amazon-aurora-global-database-writer-endpoint/>)

Author: Raunak Gupta

Published: 2026-11-11T22:01:27Z

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>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.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>), [authentication](<https://devfeed.tech/tags/authentication.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cross](<https://devfeed.tech/tags/cross.md>), [database](<https://devfeed.tech/tags/database.md>), [failover](<https://devfeed.tech/tags/failover.md>), [global](<https://devfeed.tech/tags/global.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [iam](<https://devfeed.tech/tags/iam.md>), [id](<https://devfeed.tech/tags/id.md>), [passwordless](<https://devfeed.tech/tags/passwordless.md>), [policy](<https://devfeed.tech/tags/policy.md>), [primary](<https://devfeed.tech/tags/primary.md>), [region](<https://devfeed.tech/tags/region.md>), [resource](<https://devfeed.tech/tags/resource.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>), [writer](<https://devfeed.tech/tags/writer.md>)

### AI overview

A stable Aurora Global Database writer endpoint handles routing after a cross-Region promotion, while IAM authentication requires the token's SigV4 signing Region and `rds-db:connect` authorization to match the new primary. The walkthrough discovers the current primary Region through `describe-global-clusters`, signs a token for it, and lists each Regional cluster resource ID in the IAM policy; this keeps connections working with the same endpoint and policy after switchover or failover. IAM authentication must be enabled on both clusters, clients need cross-Region network access and TLS, and discovery needs a healthy Region during an impairment. Managed failover may lose writes not yet replicated and requires compatible engine versions. The excerpt also advises caching Region discovery to limit throttling, refreshing tokens per connection because they expire after 15 minutes, and respecting DNS TTL. AWS Advanced Drivers can automate token handling; the JDBC wrapper additionally supports Global Database failover reconnection.

### Source excerpt

Learn how to combine the Amazon Aurora Global Database writer endpoint with IAM database authentication so that passwordless access survives a cross-Region switchover or failover with no configuration changes. This walkthrough signs the token for the dynamically discovered primary Region and scopes the policy to every Regional cluster resource ID.

## Build an Oracle AWR-style report for RDS/Aurora PostgreSQL

DevFeed: [Build an Oracle AWR-style report for RDS/Aurora PostgreSQL](<https://devfeed.tech/articles/build-an-oracle-awr-style-report-for-rds-aurora-postgresql-129581.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-an-oracle-awr-style-report-for-rds-aurora-postgresql/>)

Author: Tushar Rajput

Published: 2026-11-11T18:20:16Z

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>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Insight for DBAs](<https://devfeed.tech/topics/insight-for-dbas.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.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-rds](<https://devfeed.tech/tags/amazon-rds.md>), [based](<https://devfeed.tech/tags/based.md>), [build](<https://devfeed.tech/tags/build.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [cron](<https://devfeed.tech/tags/cron.md>), [database](<https://devfeed.tech/tags/database.md>), [event](<https://devfeed.tech/tags/event.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [ids](<https://devfeed.tech/tags/ids.md>), [load](<https://devfeed.tech/tags/load.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [performance](<https://devfeed.tech/tags/performance.md>), [pg-stat-statements](<https://devfeed.tech/tags/pg-stat-statements.md>), [post](<https://devfeed.tech/tags/post.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>), [report](<https://devfeed.tech/tags/report.md>), [style](<https://devfeed.tech/tags/style.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article presents `awr_lite`, a SQL-based AWR-style reporting solution for RDS and Aurora PostgreSQL built from `pg_stat_statements` and `pg_cron`. It stores snapshots every 15 minutes by default, samples active sessions every 10 seconds, and generates reports between snapshot IDs with load, activity, ranked SQL, segment, wait-event, and configuration sections. Installation requires PostgreSQL 14 or later, both extensions, an `rds_superuser` user, parameter changes and a reboot; objects and cron jobs must share the monitored database. Collection runs on the writer, and windows spanning statistics resets have unreliable deltas. Aurora lacks the WAL figures and restricts cron to one database per cluster; other databases need external scheduling. The sampler stores raw query text and client addresses, so the article advises reviewing exposure and report contents before sharing. CloudWatch Database Insights remains useful for continuous one-second graphical wait analysis.

### Source excerpt

PostgreSQL has no built-in Oracle AWR equivalent. This post shows how to build an AWR-style, snapshot-based performance report for Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL using pg_stat_statements and pg_cron, producing top-SQL, database-activity, wait-event, and load-profile reports between any two snapshot IDs, entirely in SQL.

## Diagnose Amazon Aurora MySQL performance using CloudWatch Database Insights

DevFeed: [Diagnose Amazon Aurora MySQL performance using CloudWatch Database Insights](<https://devfeed.tech/articles/diagnose-amazon-aurora-mysql-performance-using-cloudwatch-database-insights-129583.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/diagnose-amazon-aurora-mysql-performance-using-cloudwatch-database-insights/>)

Author: Aayushi Mittal

Published: 2026-11-11T16:46:38Z

Content type: article

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 CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [MySQL](<https://devfeed.tech/topics/mysql.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>), [table-partitioning](<https://devfeed.tech/topics/table-partitioning.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>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [database](<https://devfeed.tech/tags/database.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [mysql-performance](<https://devfeed.tech/tags/mysql-performance.md>), [performance](<https://devfeed.tech/tags/performance.md>)

### AI overview

CloudWatch Database Insights represents database activity as average active sessions (DB load), plots it against Max vCPU, and breaks it down by wait event and top SQL. Sustained load above capacity suggests queuing, though lock waits can stall work even below that line. The article recommends tracing dominant waits to correlated SQL before changing the system: tune CPU-heavy queries; use EXPLAIN and indexes for table reads; batch Aurora redo-log writes; reduce hot-key contention and transaction length for SYNCH waits; use connection pooling for connection churn; and limit or paginate results when client-return waits dominate. Scaling or Aurora replicas are options when CPU remains the bottleneck after tuning. Standard mode provides per-instance views and seven days of history; Advanced mode adds fleet monitoring and past-period analysis, with additional cost. Fleet triage ranks instances by load before drilling into waits and SQL.

### Source excerpt

When an Aurora MySQL or Amazon RDS for MySQL database slows down, it can be hard to tell why. This post shows how to read DB load in Amazon CloudWatch Database Insights, interpret the most common MySQL wait events, and turn each into a concrete action, so you can fix the real bottleneck instead of scaling up to a larger instance.

## ReinDB: read-only performance monitoring for PostgreSQL, first database free

DevFeed: [ReinDB: read-only performance monitoring for PostgreSQL, first database free](<https://devfeed.tech/articles/reindb-read-only-performance-monitoring-for-postgresql-first-database-free-119626.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/reindb-read-only-performance-monitoring-for-postgresql-first-database-free-3432/>)

Published: 2026-11-05T00:00:00Z

Content type: release

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [database monitoring](<https://devfeed.tech/topics/database-monitoring.md>), [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [database](<https://devfeed.tech/tags/database.md>), [first](<https://devfeed.tech/tags/first.md>), [free](<https://devfeed.tech/tags/free.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [linux](<https://devfeed.tech/tags/linux.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [mysql](<https://devfeed.tech/tags/mysql.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [performance](<https://devfeed.tech/tags/performance.md>), [performance-monitoring](<https://devfeed.tech/tags/performance-monitoring.md>), [pg-stat-statements](<https://devfeed.tech/tags/pg-stat-statements.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

ReinDB monitors PostgreSQL performance by learning each database's and statement's hour-by-hour baseline from pg_stat_statements, then flagging deviations ranked by the extra database time they cost. Flags include supporting evidence such as plan history and a testable fix script with an undo for each step. It requires one read-only login and installs nothing in the database. It can run hosted, onsite on Linux or Windows, or in the customer's AWS or Google Cloud account; MySQL, SQL Server, and Oracle are also supported. The first database is free for one person with no time limit or card requirement.

### Source excerpt

Bandlei has released ReinDB, read-only performance monitoring for PostgreSQL, self-managed or on Amazon RDS and Aurora. ReinDB learns what normal looks like for each database and statement, hour by hour, using pg_stat_statements, and flags what drifts from it, ranked by the extra database time each change costs. Each flag shows the evidence, including plan history, and a fix script your DBA can test, with an undo for each step. ReinDB installs nothing in your database and needs one read-only login. It runs hosted, onsite on Linux or Windows, or in your own AWS or Google Cloud account. MySQL, SQL Server and Oracle are also supported. The first database is free for one person, with no time limit and no card. A free 109-page guide, Rein In Your Database, covers the tuning method behind it. More at reindb.com.

## Implementing PostgreSQL logical replication between Amazon RDS for PostgreSQL instances on separate AWS Outposts

DevFeed: [Implementing PostgreSQL logical replication between Amazon RDS for PostgreSQL instances on separate AWS Outposts](<https://devfeed.tech/articles/implementing-postgresql-logical-replication-between-amazon-rds-for-postgresql-instances-on-separate-aws-outposts-119354.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/compute/implementing-postgresql-logical-replication-between-amazon-rds-for-postgresql-instances-on-separate-aws-outposts/>)

Author: Belma Canik

Published: 2026-11-04T22:02:23Z

Content type: tutorial

Language: en

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

Topics: [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [AWS Outposts](<https://devfeed.tech/topics/aws-outposts.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [all](<https://devfeed.tech/tags/all.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-outposts](<https://devfeed.tech/tags/aws-outposts.md>), [backups](<https://devfeed.tech/tags/backups.md>), [configure](<https://devfeed.tech/tags/configure.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [environment](<https://devfeed.tech/tags/environment.md>), [gateways](<https://devfeed.tech/tags/gateways.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [implementing](<https://devfeed.tech/tags/implementing.md>), [logical](<https://devfeed.tech/tags/logical.md>), [logical-replication](<https://devfeed.tech/tags/logical-replication.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>), [replication](<https://devfeed.tech/tags/replication.md>), [separate](<https://devfeed.tech/tags/separate.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

PostgreSQL logical replication between Amazon RDS instances on separate AWS Outposts can keep replication traffic on premises when CoIP addresses route through each rack's Local Gateway and the on-premises network. The setup requires CoIP to be explicitly enabled for each RDS instance, cross-Outpost and same-Outpost hairpin routes, PostgreSQL access on port 5432, and matching table schemas. Enable `rds.logical_replication` on the publisher; grant the replication user `SELECT` on published tables; and include `sslmode=require` in the subscription connection string because RDS PostgreSQL 15+ enforces SSL by default. Monitor replication and synchronization with PostgreSQL's replication status views. The approach provides a manually managed resilience option where regional backups are unacceptable or Multi-AZ prerequisites are unavailable. Multi-AZ offers automatic failover and synchronous replication, but requires Outposts in different Availability Zones and does not support local backups. Local RDS backups require S3 on Outposts capacity and are not supported for Multi-AZ deployments or read replicas.

### Source excerpt

Learn how to configure PostgreSQL logical replication between two Amazon RDS for PostgreSQL instances on separate AWS Outposts racks, keeping all replication traffic and backups within your on-premises environment by using Customer-owned IP addresses and Local Gateways, without any data traversing the AWS Region.

## Build an organization-wide Amazon RDS posture dashboard with Kiro

DevFeed: [Build an organization-wide Amazon RDS posture dashboard with Kiro](<https://devfeed.tech/articles/build-an-organization-wide-amazon-rds-posture-dashboard-with-kiro-115549.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/build-an-organization-wide-amazon-rds-posture-dashboard-with-kiro/>)

Author: Sam Mukherjee

Published: 2026-11-03T16:38:19Z

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>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Amazon Aurora](<https://devfeed.tech/topics/amazon-aurora.md>), [AWS Organizations](<https://devfeed.tech/topics/aws-organizations.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [kiro](<https://devfeed.tech/tags/kiro.md>), [organization](<https://devfeed.tech/tags/organization.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The solution collects existing AWS posture events from five services into one organization-wide Amazon CloudWatch dashboard for RDS and Aurora. It shows the latest status per resource for deletion protection, Multi-AZ, and backups, plus engine/version details where available, protection changes with principal and source IP, and engines nearing end of standard support. Member accounts forward events directly to a central EventBridge bus; CloudWatch Logs, metric filters, alarms, and dashboard widgets provide the view without a maintained Lambda or separate database. A baseline seed fills the pre-deployment gap. The transition alarm is suited to paging when protection is disabled; the recurring Security Hub state alarm serves as a reminder. The dashboard is read-only, near real-time, and relies on events within its time range; Security Hub CSPM and AWS Config remain authoritative inventory sources. Deployment requires several configured AWS services, and the Trusted Advisor feed requires an eligible support plan. In the tested account, estimated custom-metric costs were $15-$45 monthly, with a stated worst case around $90.

### Source excerpt

Deletion protection on an Amazon RDS database is a single setting that anyone can switch off, and across hundreds of accounts there is no single place to see which databases still run without it. This post shows how to track Amazon RDS posture organization-wide with one Amazon CloudWatch dashboard, built and verified with Kiro.

## How Vestiaire Collective achieved near-zero downtime RDS for MariaDB upgrades with Amazon RDS Blue/Green Deployments

DevFeed: [How Vestiaire Collective achieved near-zero downtime RDS for MariaDB upgrades with Amazon RDS Blue/Green Deployments](<https://devfeed.tech/articles/how-vestiaire-collective-achieved-near-zero-downtime-rds-for-mariadb-upgrades-with-amazon-rds-blue-green-deployments-102231.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-vestiaire-collective-achieved-near-zero-downtime-rds-for-mariadb-upgrades-with-amazon-rds-blue-green-deployments/>)

Author: Ejaz Azeem

Published: 2026-10-26T17:19:34Z

Content type: article

Language: en

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

Topics: [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [blue-green deployment](<https://devfeed.tech/topics/blue-green-deployment.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [MariaDB](<https://devfeed.tech/topics/mariadb.md>), [downtime](<https://devfeed.tech/topics/downtime.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>)

Tags: [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.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>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [downtime](<https://devfeed.tech/tags/downtime.md>), [mariadb](<https://devfeed.tech/tags/mariadb.md>), [rds-for-mariadb](<https://devfeed.tech/tags/rds-for-mariadb.md>), [upgrades](<https://devfeed.tech/tags/upgrades.md>)

### AI overview

Vestiaire Collective upgraded its Amazon RDS for MariaDB fleet from 10.6 to 10.11 and then 11.4 during peak sales season using Blue/Green Deployments. The switchovers took about 94 seconds and 7 seconds, respectively; the second caused no noticeable database write downtime, though DNS propagation took additional time. The team tested the process in nonproduction, warmed the green environment's storage and buffer pool, and ran the upgraded database alongside production writes for over a week before switching. For the first cutover, they stopped the two AWS DMS tasks and resumed them from a new binlog position afterward. AWS Countdown Premium supported readiness reviews, runbook planning, and on-call coordination. The article contrasts this approach with in-place upgrades, which it says would require hours of downtime, and notes that an AWS DMS-based upgrade was set aside due to replication-consistency complexity.

### Source excerpt

Vestiaire Collective, a global platform for pre-owned luxury fashion, achieved near-zero downtime upgrading its Amazon RDS for MariaDB fleet across two major versions. Learn how the team used Amazon RDS Blue/Green Deployments with AWS Countdown Premium to deliver a 94-second and then a 7-second switchover during peak sales season.

## Zero-Downtime Postgres Migration from RDS to Prisma Postgres

DevFeed: [Zero-Downtime Postgres Migration from RDS to Prisma Postgres](<https://devfeed.tech/articles/zero-downtime-postgres-migration-from-rds-to-prisma-postgres-100727.md>)

Original publisher: [Read original article](<https://www.prisma.io/blog/moving-prismas-control-plane-to-prisma-postgres>)

Author: Kristof Siket; Ankur Datta

Published: 2026-10-26T00:00:00Z

Content type: tutorial

Language: en

Sources: [Prisma](<https://devfeed.tech/sources/prisma-blog.md>)

Topics: [zero downtime deployment](<https://devfeed.tech/topics/zero-downtime-deployment.md>), [Prisma](<https://devfeed.tech/topics/prisma.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [control-plane](<https://devfeed.tech/topics/control-plane.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [logical](<https://devfeed.tech/tags/logical.md>), [logical-replication](<https://devfeed.tech/tags/logical-replication.md>), [migration](<https://devfeed.tech/tags/migration.md>), [open](<https://devfeed.tech/tags/open.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [prisma](<https://devfeed.tech/tags/prisma.md>), [rds](<https://devfeed.tech/tags/rds.md>), [replication](<https://devfeed.tech/tags/replication.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [tables](<https://devfeed.tech/tags/tables.md>), [using](<https://devfeed.tech/tags/using.md>), [with](<https://devfeed.tech/tags/with.md>), [zero](<https://devfeed.tech/tags/zero.md>)

### AI overview

Prisma moved its 83-table, 74 GB control-plane database from Amazon RDS to Prisma Postgres without pausing writes. Logical replication copied the tables and then streamed row changes; after checking primary keys, schema parity, network access, and per-table row counts, the team switched all six services in one deployment. The last service write reached RDS seven minutes later. A replication slot created just before cutover let RDS follow Prisma Postgres for a week, enabling rollback by changing the connection configuration. The team used `copy_data = false` and Postgres 16's `origin = none` to avoid recopying rows during reverse replication. The process required matching schemas on both databases because logical replication carries row changes, not DDL or sequence values. One migration initially ran only on Prisma Postgres and stopped the reverse stream until the SQL was applied to RDS; no data was lost.

### Source excerpt

How Prisma migrated 83 tables and 74 GB from Amazon RDS to Prisma Postgres with zero downtime using logical replication, and kept a rollback open for a week.

## Troubleshooting Data Mismatches with tablediff on Amazon RDS for SQL Server

DevFeed: [Troubleshooting Data Mismatches with tablediff on Amazon RDS for SQL Server](<https://devfeed.tech/articles/troubleshooting-data-mismatches-with-tablediff-on-amazon-rds-for-sql-server-95993.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/troubleshooting-data-mismatches-with-tablediff-on-amazon-rds-for-sql-server/>)

Author: Kanchan Bhattacharyya

Published: 2026-10-22T16:33:04Z

Content type: article

Language: en

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

Topics: [RDS for SQL Server](<https://devfeed.tech/topics/rds-for-sql-server.md>), [read-replica](<https://devfeed.tech/topics/read-replica.md>), [sql-server](<https://devfeed.tech/topics/sql-server.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [2022](<https://devfeed.tech/tags/2022.md>), [2025](<https://devfeed.tech/tags/2025.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.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-rds](<https://devfeed.tech/tags/amazon-rds.md>), [amazon-simple-storage-service-amazon-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-amazon-s3.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [audit](<https://devfeed.tech/tags/audit.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [lag](<https://devfeed.tech/tags/lag.md>), [rds-for-sql-server](<https://devfeed.tech/tags/rds-for-sql-server.md>), [read-replica](<https://devfeed.tech/tags/read-replica.md>), [replication](<https://devfeed.tech/tags/replication.md>), [scripts](<https://devfeed.tech/tags/scripts.md>), [sql-server](<https://devfeed.tech/tags/sql-server.md>), [t-sql](<https://devfeed.tech/tags/t-sql.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>), [utility](<https://devfeed.tech/tags/utility.md>)

### AI overview

After an Amazon RDS for SQL Server read replica catches up, tablediff can provide independent row-level parity evidence that replication metrics alone do not: compare the primary and replica only after `ReplicaLag`, `redo_queue_size`, and `log_send_queue_size` are all zero. Run it from a Windows EC2 client with access to both endpoints; target tables need a clustered primary key or unique index. It reports source-only, destination-only, and column-mismatched rows, and can generate T-SQL fixes. The replica is read-only, so remediation requires promotion, which is irreversible; regenerate the fix script after promotion and wrap its bare DML statements in an explicit transaction with a validation gate. Re-run tablediff to confirm zero differences. A fresh rebuild may be preferable for extensive or structural divergence. Comparisons scan whole tables and can give misleading results during active writes or redo, so run during a quiet period after queues drain.

### Source excerpt

Learn how to use the SQL Server tablediff utility to validate an Amazon RDS for SQL Server read replica against its primary after a replication lag event, detect and classify row-level data mismatches, and apply auditable T-SQL fix scripts on a promoted replica instance.

## SafeGrd: PostgreSQL backups that are restored and checked on a schedule

DevFeed: [SafeGrd: PostgreSQL backups that are restored and checked on a schedule](<https://devfeed.tech/articles/safegrd-postgresql-backups-that-are-restored-and-checked-on-a-schedule-100723.md>)

Original publisher: [Read original article](<https://www.postgresql.org/about/news/safegrd-postgresql-backups-that-are-restored-and-checked-on-a-schedule-3414/>)

Published: 2026-10-22T00:00:00Z

Content type: article

Language: en

Sources: [PostgreSQL news](<https://devfeed.tech/sources/postgresql-news.md>)

Topics: [backups](<https://devfeed.tech/topics/backups.md>), [RDS for PostgreSQL](<https://devfeed.tech/topics/rds-for-postgresql.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [backups](<https://devfeed.tech/tags/backups.md>), [counts](<https://devfeed.tech/tags/counts.md>), [decrypt](<https://devfeed.tech/tags/decrypt.md>), [dump](<https://devfeed.tech/tags/dump.md>), [email](<https://devfeed.tech/tags/email.md>), [encrypted](<https://devfeed.tech/tags/encrypted.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [fire](<https://devfeed.tech/tags/fire.md>), [image](<https://devfeed.tech/tags/image.md>), [lock](<https://devfeed.tech/tags/lock.md>), [managed](<https://devfeed.tech/tags/managed.md>), [memory](<https://devfeed.tech/tags/memory.md>), [neon](<https://devfeed.tech/tags/neon.md>), [null](<https://devfeed.tech/tags/null.md>), [pg-dump](<https://devfeed.tech/tags/pg-dump.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-backups](<https://devfeed.tech/tags/postgresql-backups.md>), [schedule](<https://devfeed.tech/tags/schedule.md>)

### AI overview

SafeGrd backs up PostgreSQL 13+ from a nearby host using a read-only database role, encrypts data locally with age, and stores it in an S3 bucket with Object Lock; after the first run, backups upload only changes. Scheduled "Fire Drills" decrypt the newest backup and check it either in memory or in a throwaway PostgreSQL database, including recorded counts, extensions, and optional user SQL checks. Signed, linked records can be verified in a browser. Customers choose customer-managed keys, which only they can decrypt, or SafeGrd-managed keys released to enrolled hosts. The free plan covers one database, with daily hosted backups or hourly backups to a customer bucket and weekly in-memory drills; paid plans start at $15/month and add hourly backups, sandbox drills, and more databases.

### Source excerpt

SafeGrd is a new backup service for PostgreSQL 13 and later that restores every backup on a schedule and checks the row counts. It takes a backup, restores it later into memory or a throwaway database, and counts what came back, so you find out a backup is broken before you need it. Taking the backup The safegrd daemon runs on a host next to your database and connects as a read-only role. On PostgreSQL 14 and later that role only needs pg_read_all_data. On 13 you grant each schema instead. The schema comes from pg_dump and the rows come over binary COPY, in one transaction. After the first run, each backup uploads only what changed. The backup is encrypted with age on your host before it leaves, then written to an S3 bucket with Object Lock on. That can be your own bucket or SafeGrd-hosted storage. The backup data never goes through SafeGrd's servers. You choose how the age key is managed. With a customer-managed key, only you can decrypt these backups. With a SafeGrd-managed key, SafeGrd keeps your key sealed and releases it only to your enrolled hosts, so you can restore even after losing a host. Supabase, Neon and Amazon RDS work from a connection string. Supabase backups are restored on Supabase's own Postgres image, so the extensions in the dump load. Testing the backup We call the restore test a Fire Drill. It takes the newest backup, decrypts it and checks it in one of two ways: In memory. The dump is replayed without a running server, and the table, row and column counts and the extensions are compared with what the backup recorded. In a sandbox. The backup is restored into a throwaway PostgreSQL database and the counts are checked there. You can add your own SQL checks too, for example SELECT count(*) FROM users WHERE email IS NULL has to return 0. Each drill writes a signed, dated record with the counts and the check results. Every record points at the one before it. The attestation verifier checks the whole chain against SafeGrd's published signing key in

## How U.S. Bank migrated 119 TB from Oracle Exadata to Amazon RDS for Oracle

DevFeed: [How U.S. Bank migrated 119 TB from Oracle Exadata to Amazon RDS for Oracle](<https://devfeed.tech/articles/how-u-s-bank-migrated-119-tb-from-oracle-exadata-to-amazon-rds-for-oracle-91267.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/how-u-s-bank-migrated-119-tb-from-oracle-exadata-to-amazon-rds-for-oracle/>)

Author: Benjamin Wessling

Published: 2026-10-20T15:53:13Z

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>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>), [NVMe](<https://devfeed.tech/topics/nvme.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [amazon-rds](<https://devfeed.tech/tags/amazon-rds.md>), [automated](<https://devfeed.tech/tags/automated.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-datasync](<https://devfeed.tech/tags/aws-datasync.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [bandwidth](<https://devfeed.tech/tags/bandwidth.md>), [bank](<https://devfeed.tech/tags/bank.md>), [copy](<https://devfeed.tech/tags/copy.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [data](<https://devfeed.tech/tags/data.md>), [data-loss](<https://devfeed.tech/tags/data-loss.md>), [databases](<https://devfeed.tech/tags/databases.md>), [days](<https://devfeed.tech/tags/days.md>), [exadata](<https://devfeed.tech/tags/exadata.md>), [intermediate-200](<https://devfeed.tech/tags/intermediate-200.md>), [migration](<https://devfeed.tech/tags/migration.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [rds-for-oracle](<https://devfeed.tech/tags/rds-for-oracle.md>)

### AI overview

U.S. Bank moved four Oracle Exadata databases totaling about 119 TB to Amazon RDS for Oracle using Oracle XTTS, AWS DataSync and Amazon EFS. Its automated, config-driven pipeline used full and incremental block backups while production remained online, then a final sync and import during cutover. DataSync's observed in-flight compression and scheduled bandwidth throttling helped transfer the baseline in about seven days over a shared, bandwidth-limited Direct Connect link; the bank reported zero data loss and cutovers averaging roughly four hours per database. The 7-day figure covers the baseline copy, while migrations and staggered cutovers spanned several weeks. Preparation included reorganizing tablespaces exceeding RDS's 16 TB bigfile limit, sizing for HCC decompression, and checking Oracle timezone, character-set and compatibility requirements. The account also describes post-migration tuning for differences from Exadata.

### Source excerpt

U.S. Bank migrated 119 TB across four Oracle Exadata databases to Amazon RDS for Oracle over a bandwidth-limited AWS Direct Connect link. This post walks through the automated migration pipeline they built with Oracle Transportable Tablespaces (XTTS), AWS DataSync, and Amazon EFS, completing the initial baseline copy in 7 days with zero data loss.

[Next page](<https://devfeed.tech/topics/amazon-rds.md?cursor=WyIyMDI2LTEwLTIwVDE1OjUzOjEzKzAwOjAwIiwgIjYwMjEzNjlkLTNiZjctNDM1YS1hMDljLWQ2YWM4MGI5ODIwYyJd>)