OffNet Newsroom

Daily topic roundup

AWS

Wednesday, August 19, 2026 · 8 stories, curated & summarized — click any story for the source.

AWS has updated Aurora Serverless to automatically add 12 Aurora Capacity Units within a single second, allowing the cluster to scale up to 256 ACUs rapidly. The blog post demonstrates this responsiveness against sudden workload spikes and benchmarks the throughput against a provisioned db.r8g.xlarge instance. This enhancement targets agentic AI and other variable traffic patterns requiring immediate compute availability.

  • Aurora Serverless now adds 12 ACUs per second, reaching 256 ACUs total capacity quickly.
  • Designed specifically to handle spiky workloads like agentic AI inference tasks.
  • Performance benchmarks compare new scaling speed against provisioned db.r8g.xlarge instances.
  • Reduces latency risk for applications with unpredictable or bursty database demand.
BY THE NUMBERSAurora Serverless Scaling Speed256 ACUsMax capacity in one secondAdds 12 ACUs/sec for spiky workloads
AWS Database Blog awsdatabase

AWS DMS now supports Oracle Materialized Views with Fast Refresh

AWS Database Blog details configuring Oracle Materialized Views with Fast Refresh and materialized view logs to enable incremental CDC replication via AWS DMS. This method avoids full-reload overhead, allowing near real-time migration of large, multi-table joined views to AWS without performance penalties.

  • Enable Fast Refresh and materialized view logs on source Oracle DBs
  • Use AWS DMS for incremental CDC instead of full table reloads
  • Supports efficient migration of complex multi-table joined views
  • Achieves near real-time replication for large datasets
AWS Database Blog awsdatabase

AWS Streams Aurora DSQL CDC to Apache Iceberg via Firehose

AWS introduces a pattern to stream Amazon Aurora DSQL change data capture events directly into Apache Iceberg tables stored on Amazon S3 using Amazon Data Firehose. The solution enables real-time analytics by allowing queries against the data via Amazon Athena. It utilizes a two-table design to maintain both a full audit trail and a current-state view for practitioners.

  • Use Amazon Data Firehose to bridge Aurora DSQL CDC and S3-hosted Iceberg tables.
  • Query ingested data in real-time using Amazon Athena for analytics workflows.
  • Implement a two-table design to separate current state from full audit history.
  • Leverages managed services to reduce custom ETL engineering overhead.

A follow-up analysis from Hugging Face reveals that simply changing the execution order of jobs within the same cluster significantly improved resource utilization. By optimizing how workloads are sequenced rather than adding hardware, they achieved a 33-point gain in efficiency. This demonstrates that scheduling logic is a critical lever for maximizing GPU fleet performance.

  • Reordering existing jobs yielded a 33-point utilization increase without hardware changes.
  • Scheduling logic is as critical as capacity for maximizing GPU fleet efficiency.
  • Optimization efforts should prioritize execution order before scaling infrastructure.

Amazon Web Services has extended Amazon Bedrock AgentCore with a new persistent compute option designed for long-running, complex AI agent workflows. This runtime instance capability provides dedicated infrastructure specifically for multi-agent coordination tasks. The addition supports more stable execution environments for agents that require state maintenance over extended periods.

  • Persistent compute instances replace ephemeral setups, supporting long-running multi-agent coordination.
  • Agents now have dedicated infrastructure tailored for complex, stateful workflows.
  • Bedrock AgentCore runtime instances simplify orchestration of persistent AI tasks.
  • This feature targets use cases requiring stable, long-lived agent execution environments.

Amazon Quick now blocks new AI features by default for users assigned to specific custom permission profiles. Administrators must explicitly allow each capability, shifting from a reactive post-release model to proactive governance. This setting restricts both upcoming and existing capabilities within the targeted category until approved.

  • Governance shifts from reactive to proactive by blocking new AI features at launch
  • Restrictions apply only to the specific custom permission profile configured
  • Existing capabilities in restricted categories are also blocked until explicitly allowed
  • Configure via Amazon Quick Manage account or AWS CLI for granular control
HOW IT WORKSProactive AI Governance Flow1Admin enables deny-by-default2New AI features blocked3Explicit approval required4Feature access granted

Amazon Bedrock now supports OpenAI GPT-5.6 models via the bedrock-runtime endpoint, exposing Responses, Converse, and Chat Completions APIs. The update introduces cross-region inference to boost throughput and reduce costs by routing requests across multiple AWS regions. Geo inference options allow data to remain within specific boundaries, such as the new US Geo scope, while global inference serves requests from any region.

  • GPT-5.6 (Sol, Terra, Luna) models are now available on Bedrock via standard OpenAI-compatible APIs.
  • Cross-region inference automates request routing to maximize throughput without manual capacity management.
  • Geo cross-region inference keeps data within predefined boundaries, including new US Geo support.
  • Global cross-region inference allows requests to be served from any commercial region for maximum scalability.
HOW IT WORKSBedrock Inference Routing1User sends API request2Bedrock receives request3Route to optimal region4GPT-5.6 model processes5Return response to user

Amazon EC2 Auto Scaling now allows terminating up to 100 instances in a single API call via TerminateInstanceInAutoScalingGroup. This reduces API overhead for workloads requiring fast scale-downs, such as AI training or container orchestrators. The operation validates all instance IDs atomically and preserves existing behaviors like lifecycle hooks and load balancer draining.

  • Reduce API call volume when scaling down large fleets by batching up to 100 instances.
  • Atomic validation ensures all IDs are valid before any termination begins.
  • Existing Auto Scaling features like lifecycle hooks remain active for each instance.
  • Ideal for event-driven architectures or AI jobs needing rapid fleet reduction.
  • Available in all AWS Regions at no additional cost.
BY THE NUMBERSBatch Termination Scale100Instances per single API callReduces overhead for rapid fleet scale-downs
↑