AWS

Amazon RDS for PostgreSQL 19 Beta 4 is now accessible in the Database Preview Environment for evaluation. This release refines query performance and autovacuum management from previous betas, addressing stability issues and bugs. Key fixes include corrected freeze-score scaling for autovacuum prioritization and improved reporting for TOAST tables in pg_stat_autovacuum_scores.

• Test PostgreSQL 19 Beta 4 in the RDS Preview Environment for early compatibility checks.
• Autovacuum maintenance on large tables now shares rebalanced cost limits across workers.
• Tune autovacuum prioritization using corrected freeze-score scaling logic.
• Check pg_stat_autovacuum_scores for accurate TOAST table reporting.

Amazon RDS for PostgreSQL versions 18 and higher now support post-quantum TLS (PQ-TLS) key exchange to encrypt data in transit. Users can modify the ssl_groups parameter to select cryptographic groups from an AWS allow list. This feature allows organizations to align their database encryption standards with post-quantum security requirements.

• Available on RDS for PostgreSQL versions 18 and higher
• Modify ssl_groups parameter to enable post-quantum TLS
• Select from AWS-approved cryptographic groups for compliance
• Secures data in transit against future quantum threats

Amazon RDS for MySQL has released new Extended Support minor versions, specifically 5.7.44-rds.20260902 and 8.0.46-rds.20260908. These updates provide up to three additional years of fixes for critical CVEs and bugs beyond the standard support lifecycle. This extension allows organizations more time to plan and execute upgrades to newer major versions without immediate service interruption.

• MySQL 5.7 and 8.0 gain extended lifecycle support through new minor releases.
• Fixes cover critical CVEs and bugs to maintain security posture longer.
• Upgrade paths include Blue/Green Deployments, in-place, or snapshot restore.
• Migration to MySQL 8.4 remains supported via AWS DMS from external sources.

AWS now allows Amazon EMR on EKS to run big data workloads on IPv6-enabled EKS clusters. This update lets analytics teams deploy Apache Spark and Flink jobs without relying on IPv4 conservation tactics like secondary CIDRs. The expanded address space supports high-executor scenarios, enabling concurrent execution of large jobs without address planning constraints.

• EMR on EKS now integrates with IPv6 EKS clusters for Spark and Flink.
• Eliminates need for IPv4 workarounds like secondary CIDR ranges.
• Supports 500+ executor jobs concurrently without address limit planning.
• Scales analytics workloads using the vast IPv6 address space.

AWS has made Route 53 Resolver generally available on second-generation Outposts racks, enabling managed recursive DNS resolution directly at the edge. This feature allows workloads to resolve queries locally, which reduces latency and removes the dependency on the Service Link to the parent AWS Region. The service runs on AWS-managed infrastructure embedded in the hardware, requiring no customer compute, and maintains cached records during connectivity outages to ensure continuous resolution.

• Local DNS resolution eliminates latency and Service Link dependency for Outpost workloads.
• Continuous resolution is maintained during connectivity interruptions via cached records.
• No customer compute capacity is required; it runs on embedded AWS-managed infrastructure.
• Enabled by default on multi-rack Gen2 Outposts; self-managed DNS remains an option.

Amazon EMR 7.14 launches with upgraded Apache Spark 3.5.8 and Iceberg 1.10.1 across EC2, EKS, and Serverless. Materialized views now leverage change data capture for faster refreshes on tables with updates or deletes. EKS clusters gain Spark Connect endpoints with token-based auth and IPv6 support, while Serverless shuffle limits rise to 1 TiB.

• Iceberg materialized views use CDC to refresh only affected data files, speeding up updates.
• Spark 3.5.8 and Iceberg 1.10.1 are now default versions across all EMR deployment modes.
• EMR on EKS supports Spark Connect with token-based auth and IPv6 cluster workloads.
• EMR Serverless shuffle storage limit increases from 200 GiB to 1 TiB per job.
• Release is available in all AWS Regions where Amazon EMR is currently supported.

AWS has extended Amazon DynamoDB global tables with multi-Region strong consistency (MRSC) to five new regions, bringing the total supported count to 15. This update enables the creation of global tables with three replicas or two replicas plus one witness across any combination of the supported regions, including cross-continent setups. The feature allows architects to achieve a zero recovery point objective (RPO) while routing traffic to geographically closer endpoints for lower latency.

• MRSC now supports 15 regions, including Canada Central, Stockholm, Spain, Mumbai, and Singapore.
• Configurations allow for three replicas or two replicas with one witness region across supported areas.
• Cross-continent deployments are now possible, enabling better latency routing for global users.
• The feature guarantees zero RPO for highly available multi-region applications.
• Developers can route to nearby endpoints to optimize performance while maintaining strong consistency.