# Amazon EC2 Amazon Elastic Compute Cloud is an AWS cloud computing service that provides resizable, secure compute capacity as virtual servers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## New low-cost burstable Amazon EC2 T8i instances are generally available DevFeed: [New low-cost burstable Amazon EC2 T8i instances are generally available]() Original publisher: [Read original article]() Author: Channy Yun (윤석찬) Published: 2026-09-17T21:11:48Z Content type: release Language: en Sources: [AWS News Blog]() Topics: [Amazon EC2](), [amazon](), [intel](), [Nitro System](), [Development](), [Microservice](), [migration](), [Availability]() Tags: [amazon](), [amazon-ec2](), [aws](), [compute](), [cost](), [cpu](), [ec2](), [infrastructure](), [intel](), [intel-xeon](), [launch](), [microservices](), [migration](), [news](), [performance](), [testing]() ### AI overview AWS announces the general availability of low-cost, burstable Amazon EC2 T8i instances powered by custom sixth-generation Intel Xeon Scalable Processors. The instances target lightweight and moderate CPU workloads and offer up to 30% better price performance than previous-generation T3 instances. ### Source excerpt AWS introduces new low-cost burstable Amazon EC2 T8i instances powered by custom sixth generation Intel Xeon Scalable Processors (Granite Rapids), available only on AWS. T8i instances are among the lowest-cost EC2 instances and deliver up to 30% better price performance over previous generation T3 instances. ## Multi-modal autoscaling with Amazon EC2 Auto Scaling: adding signals for faster, more reliable scaling DevFeed: [Multi-modal autoscaling with Amazon EC2 Auto Scaling: adding signals for faster, more reliable scaling]() Original publisher: [Read original article]() Author: Shubhendu Dubey Published: 2026-09-17T18:18:38Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [autoscaling](), [Amazon EC2](), [scaling](), [Amazon CloudWatch](), [Amazon Web Services](), [AWS CloudFormation](), [Deployment](), [dashboards]() Tags: [advanced-300](), [amazon-cloudwatch](), [amazon-ec2](), [api](), [auto-scaling](), [autoscaling](), [aws](), [aws-cloudformation](), [deployment](), [forecasting](), [latency](), [load](), [load-balancer](), [scaling](), [technical-how-to]() ### AI overview This tutorial explains multi-modal autoscaling with Amazon EC2 Auto Scaling by combining CPU, request-count, application-level, and predictive signals. It describes a controlled test in which application metrics avoided rejected checkout sessions and reduced p99 latency compared with CPU-only scaling. ### Source excerpt Multi-modal autoscaling with Amazon EC2 Auto Scaling combines infrastructure metrics like CPU with application-level signals, so a group scales on the demand its users create. In this post, we show you how to implement it, with code samples and results from a controlled test. ## Resolve Amazon Aurora PostgreSQL lock contention with Database Insights: Part 2 DevFeed: [Resolve Amazon Aurora PostgreSQL lock contention with Database Insights: Part 2]() Original publisher: [Read original article]() Author: Sameer Kumar Published: 2026-09-14T16:02:16Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [Amazon Aurora](), [Amazon CloudWatch](), [PostgreSQL](), [Concurrency](), [Monitoring](), [Database](), [Amazon EC2](), [Architecture & Design](), [Amazon Web Services](), [AWS CloudFormation]() Tags: [advanced-300](), [amazon-aurora](), [amazon-cloudwatch](), [amazon-ec2](), [aws](), [aws-cloudformation](), [concurrency](), [monitoring](), [performance](), [postgresql](), [rds-for-postgresql](), [simulation](), [technical-how-to]() ### AI overview This tutorial explains how to diagnose and resolve lock contention in Amazon Aurora PostgreSQL using Amazon CloudWatch Database Insights. It demonstrates Lock Analysis and the Lock Tree visualization for identifying blocking sessions, then covers immediate fixes, configuration changes, optimistic concurrency control, asynchronous processing, SKIP LOCKED, and row splitting. ### Source excerpt Part 1 showed how row lock contention degrades Amazon Aurora PostgreSQL throughput. In Part 2, use Amazon CloudWatch Database Insights and its Lock Tree to pinpoint blocking sessions, then resolve contention with query termination, timeout parameters, and architectural patterns such as SKIP LOCKED and row splitting that restore throughput. ## How AWS Lambda logs every flow across thousands of microVMs per host with eBPF and Rust DevFeed: [How AWS Lambda logs every flow across thousands of microVMs per host with eBPF and Rust]() Original publisher: [Read original article]() Author: Prashant Kumar Singh Published: 2026-09-11T12:00:00Z Content type: article Language: en Sources: [The New Stack]() Topics: [AWS Lambda](), [Architecture & Design](), [SIEM, Security, Observability](), [telemetry](), [Amazon EC2](), [Amazon S3](), [VPC]() Tags: [architecture](), [aws](), [aws-lambda](), [aws-marketplace](), [compliance](), [ebpf](), [firecracker](), [incident](), [incident-response](), [logs](), [monitoring](), [observability](), [post-contributed](), [rust](), [s3](), [scale](), [security](), [server](), [serverless](), [sponsor-aws-marketplace](), [sponsored-post-contributed](), [vpc]() ### AI overview AWS Lambda describes replacing an aging network-capture system with an eBPF and Rust pipeline that records network flows across short-lived, tenant-isolated microVMs. The system prioritizes complete, correctly attributed records with minimal overhead for security investigation, metering, audit, observability, and monitoring. ### Source excerpt On any compute platform, when a security alert fires, the question is always the same. Which workload talked to that The post How AWS Lambda logs every flow across thousands of microVMs per host with eBPF and Rust appeared first on The New Stack. ## Validating multi-Region DR for Terraform Enterprise with AWS FIS DevFeed: [Validating multi-Region DR for Terraform Enterprise with AWS FIS]() Original publisher: [Read original article]() Author: Frenil Randeria Published: 2026-09-09T21:05:02Z Content type: article Language: en Sources: [AWS Architecture Blog]() Topics: [Terraform](), [AWS Fault Injection Service (FIS)](), [Chaos Engineering](), [Amazon S3](), [Amazon EC2](), [Databases]() Tags: [advanced-300](), [amazon-aurora](), [amazon-ec2](), [amazon-s3](), [aws](), [aws-fault-injection-service-fis](), [disaster-recovery](), [postgresql](), [technical-how-to](), [terraform](), [validation]() ### AI overview This article explains how to validate customer-operated multi-Region disaster recovery for Terraform Enterprise on AWS using three-phase AWS FIS experiments. It covers failover and failback testing, hidden dependency discovery, and reported recovery times of 12-14 minutes. ### Source excerpt Learn how AWS, HashiCorp, and Athenahealth designed and chaos-tested a multi-Region disaster recovery strategy for Terraform Enterprise on AWS. This post walks through three-phase AWS Fault Injection Service experiments across Amazon EC2, Aurora, and Amazon S3, the 12-14 minute recovery times achieved, and the state file dependency pitfall to avoid. ## AWS Weekly Roundup: Claude Fable 5.1 on AWS, Amazon Linux 2027 preview, AWS Certified AI Business Strategist, and more (September 7, 2026) DevFeed: [AWS Weekly Roundup: Claude Fable 5.1 on AWS, Amazon Linux 2027 preview, AWS Certified AI Business Strategist, and more (September 7, 2026)]() Original publisher: [Read original article]() Author: Channy Yun (윤석찬) Published: 2026-09-07T14:24:08Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [Claude](), [Amazon Bedrock](), [anthropic](), [Amazon EC2](), [Operating system]() Tags: [amazon-bedrock](), [amazon-ec2](), [amazon-redshift](), [anthropic](), [aws](), [aws-lambda](), [aws-training-and-certification](), [claude](), [linux](), [news](), [security-identity-compliance](), [week-in-review]() ### AI overview AWS's weekly roundup announces Claude Fable 5.1 availability through Amazon Bedrock and Claude Platform on AWS, including retention and safety-review details for Covered Models. It also highlights the Amazon Linux 2027 public preview and EC2 R9g/R9gd memory-optimized instances. ### Source excerpt Last week, Claude Fable 5.1 became available on AWS. According to Anthropic, Claude Fable 5.1 delivers frontier intelligence for ambitious tasks across coding, scientific research, and enterprise workflows. Claude Fable 5.1 is built for long-running, high-stakes work that runs for hours and spans many applications. It can own more of a software project on its [...] ## Monitor self-managed databases with Amazon CloudWatch Database Insights DevFeed: [Monitor self-managed databases with Amazon CloudWatch Database Insights]() Original publisher: [Read original article]() Author: Nirupam Datta Published: 2026-09-03T18:10:43Z Content type: article Language: en Sources: [AWS Database Blog]() Topics: [Databases](), [Amazon EC2](), [dashboards]() Tags: [amazon-aurora](), [amazon-cloudwatch](), [amazon-ec2](), [amazon-rds](), [announcements](), [dashboards](), [database](), [intermediate-200](), [monitoring](), [postgresql](), [sql]() ### AI overview Amazon CloudWatch Database Insights now monitors self-managed PostgreSQL on Amazon EC2 alongside Aurora and Amazon RDS databases from one console. ### Source excerpt Amazon CloudWatch Database Insights now extends to self-managed databases. Monitor self-managed PostgreSQL on Amazon EC2 alongside your Amazon Aurora and Amazon RDS fleet from a single console, with the same DB Load, Top SQL, and wait event analysis you use for managed databases. ## AWS Launches Graviton5-Based EC2 R9g and R9gd Memory-Optimized Instances DevFeed: [AWS Launches Graviton5-Based EC2 R9g and R9gd Memory-Optimized Instances]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-01T18:42:59Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [Amazon Web Services](), [Amazon EC2](), [Arm](), [cpu](), [Hardware](), [Nitro System](), [virtualization](), [Nitro Isolation Engine](), [Database](), [Caching](), [Kubernetes](), [Formal verification]() Tags: [amazon-ec2](), [amazon-eks](), [arm](), [aws](), [c-plus-plus](), [caching](), [cloud](), [database](), [docker](), [enterprise](), [formal-verification](), [go](), [hardware](), [java](), [microservices](), [nitro-isolation-engine](), [nitro-system](), [node-js](), [nvme](), [processors](), [python](), [time]() ### AI overview AWS has generally released the Amazon EC2 R9g and R9gd instances, powered by AWS Graviton5 processors. These Arm-based, memory-optimized instances offer higher per-vCPU performance, faster memory, larger cache capacity, and increased networking and Amazon EBS bandwidth for database, caching, analytics, container, and microservices workloads. R9gd adds local NVMe SSD storage for low-latency local capacity. Both families use the AWS Nitro System and Nitro Isolation Engine, with AWS citing formal verification for the isolation properties. ### Source excerpt AWS has made its Amazon EC2 R9g and R9gd instances generally available, introducing memory-optimized systems powered by AWS Graviton5 processors. The new Arm-based instances target database, caching, analytics, container, and microservices workloads that require high memory bandwidth and improved per-vCPU performance. Compared with Graviton4-based R8g instances, AWS states that R9g can deliver up to 25% The post AWS Launches Graviton5-Based EC2 R9g and R9gd Memory-Optimized Instances appeared first on StorageReview.com. ## Amazon EC2 R9g and R9gd instances powered by AWS Graviton5 processors are now generally available DevFeed: [Amazon EC2 R9g and R9gd instances powered by AWS Graviton5 processors are now generally available]() Original publisher: [Read original article]() Author: Daniel Abib Published: 2026-08-31T19:53:34Z Content type: release Language: en Sources: [AWS News Blog]() Topics: [Amazon EC2](), [cpu](), [networking]() Tags: [amazon-ec2](), [announcements](), [aws](), [big-data](), [cache](), [compute](), [databases](), [graviton](), [hardware](), [launch](), [memory](), [networking](), [news](), [nitro-isolation-engine](), [nitro-system](), [performance](), [storage]() ### AI overview Amazon EC2 R9g and R9gd memory-optimized instances powered by AWS Graviton5 processors are generally available. The release highlights higher compute performance, faster memory, larger cache, increased network and EBS bandwidth, and local NVMe SSD storage for R9gd. ### Source excerpt Amazon EC2 R9g and R9gd instances powered by AWS Graviton5 are now generally available, delivering up to 25% better compute performance than R8g, ideal for databases, in-memory caches, and real-time analytics. ## Delivering Vera: NVIDIA's First CPU Built for Agents Is Shipping Now DevFeed: [Delivering Vera: NVIDIA's First CPU Built for Agents Is Shipping Now]() Original publisher: [Read original article]() Author: Ian Finder Published: 2026-08-27T13:00:17Z Content type: article Language: en Sources: [NVIDIA Blog]() Topics: [Vera CPU](), [cpu](), [NVIDIA Vera](), [Artificial Intelligence](), [AI Factory](), [Nvidia](), [Amazon Web Services](), [Amazon EC2](), [GPU]() Tags: [agentic-ai](), [agents](), [ai](), [ai-factory](), [ai-infrastructure](), [ai-training](), [amazon-ec2](), [aws](), [corporate](), [cpu](), [gpu](), [hardware](), [nvidia](), [nvidia-vera](), [orchestration](), [rubin-gpu](), [vera-cpu]() ### AI overview NVIDIA is shipping Vera, a CPU designed for agentic AI workloads, to AWS and other organizations across the AI ecosystem. The article describes Vera's 88 custom Olympus cores, 1.2TB/s memory bandwidth, and up to 1.8x faster per-core performance on agentic AI workloads, alongside its role in supporting concurrent CPU-intensive tasks such as tool calls, orchestration, retrieval, software testing, and data analysis. ### Source excerpt NVIDIA Vice President of Hyperscale and HPC Ian Buck hand-delivers Vera CPU systems across the AI ecosystem as Vera begins shipping at scale. ## Replication Lag on AWS FSx: The Hidden EC2 Single-Flow Bandwidth Limit DevFeed: [Replication Lag on AWS FSx: The Hidden EC2 Single-Flow Bandwidth Limit]() Original publisher: [Read original article]() Author: Pablo Svampa Published: 2026-08-25T21:00:16Z Content type: article Language: en Sources: [Blog - Percona]() Topics: [Amazon Web Services](), [PostgreSQL](), [Amazon EC2](), [Replication](), [cloud-infrastructure](), [Network](), [Monitoring]() Tags: [aws](), [database](), [ec2](), [hardware-and-storage](), [insight-for-dbas](), [monitoring](), [network](), [postgresql](), [replication](), [storage]() ### AI overview This Percona case study examines PostgreSQL replication lag on an EC2 instance using Amazon FSx over NFS. Although AWS reported healthy storage with substantial provisioned capacity remaining, vmstat showed persistent I/O blocking and wait, indicating a bottleneck somewhere across the storage and network path, including an EC2 single-flow bandwidth limit. ### Source excerpt A recent case in our Percona Support team started with a familiar complaint. A PostgreSQL standby lagging behind its primary. Although the problem was simple, it brought a specific flavor that's worth sharing. The customer had already reached out to AWS Support about the storage layer behind the database, an Amazon FSx filesystem mounted over ... Continued The post Replication Lag on AWS FSx: The Hidden EC2 Single-Flow Bandwidth Limit appeared first on Percona. ## Happy 20th Birthday, Amazon EC2 DevFeed: [Happy 20th Birthday, Amazon EC2]() Original publisher: [Read original article]() Author: Channy Yun (윤석찬) Published: 2026-08-25T16:11:02Z Content type: article Language: en Sources: [AWS News Blog]() Topics: [Amazon EC2](), [Inference Performance]() Tags: [ai-inference](), [amazon-cloudwatch](), [amazon-ec2](), [amazon-ec2-mac-instances](), [apple](), [aws](), [aws-inferentia](), [aws-local-zones](), [aws-outposts](), [aws-trainium](), [cloud](), [cloud-computing](), [general](), [generative-ai](), [graviton](), [infrastructure](), [intel](), [linux](), [news](), [nitro-system](), [performance]() ### AI overview AWS marks Amazon EC2's 20th anniversary by reviewing its evolution from a single Linux virtual-server instance to a global service with more than 1,200 instance types. The article highlights foundational services, expanded deployment options, and AWS-designed silicon for AI inference and training. ### Source excerpt On the 20th Anniversary, we recognize how AWS has continued to push the boundaries of what cloud computing can deliver, building custom silicon for general-purpose and AI workloads and expanding EC2 into new form factors and deployment models that our customers in 2006 could not have imagined. ## AWS Weekly Roundup: Student Rewards on AWS Builder Center, Local Zone in Las Vegas, and more (August 24, 2026) DevFeed: [AWS Weekly Roundup: Student Rewards on AWS Builder Center, Local Zone in Las Vegas, and more (August 24, 2026)]() Original publisher: [Read original article]() Author: Esra Kayabali Published: 2026-08-24T16:20:15Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [Amazon Web Services](), [AWS Local Zones](), [Amazon EC2](), [Availability](), [Cloud](), [Amazon Elastic Container Service](), [Amazon Elastic Kubernetes Service]() Tags: [2026](), [amazon](), [amazon-bedrock](), [amazon-ec2](), [amazon-eks](), [amazon-workspaces](), [announcements](), [availability](), [aws](), [aws-cloudshell](), [aws-glue](), [aws-local-zones](), [cloud](), [education](), [launch](), [news](), [resources](), [week-in-review]() ### AI overview This AWS Weekly Roundup highlights Student Rewards on AWS Builder Center, which gives verified higher-education students access to premium AWS Skill Builder resources and awards AWS Credits and a certification exam voucher for earning badges. It also covers a new AWS Local Zone in Las Vegas, an additional Availability Zone in the Europe (London) Region, and batch instance termination support for Amazon EC2 Auto Scaling. The supplied article text ends mid-sentence, so the summary covers only the available content. ### Source excerpt During my time at AWS, I have always looked for opportunities to work with students. I have delivered over 50 talks at universities across the region, and watching the potential in the room is always a strong motivator. It reminds me of why I do this work, and that the students I meet today may [...] ## Amazon Linux default SSM parameter will now track the latest kernel DevFeed: [Amazon Linux default SSM parameter will now track the latest kernel]() Original publisher: [Read original article]() Author: Gokul Govindaraju Published: 2026-08-20T19:49:05Z Content type: article Language: en Sources: [AWS Compute Blog]() Topics: [Linux](), [Amazon EC2](), [Amazon Web Services](), [releases](), [Latency]() Tags: [advanced-300](), [amazon](), [amazon-ec2](), [announcements](), [aws](), [kernel](), [latency](), [launch](), [linux](), [os](), [releases](), [systems](), [update](), [updates]() ### AI overview Amazon Linux's default AWS Systems Manager parameter will now track the latest validated kernel version. For Amazon Linux 2023, it moved from kernel 6.1 to 6.18 on August 17, 2026, after a validation period. New instances launched through the parameter will use the updated kernel, while running instances and version-specific parameter users are unaffected. ### Source excerpt The Amazon Linux kernel-default SSM parameter now updates to point to the latest kernel version as new releases become available. This post explains what this means for your workloads and how to manage the transition. ## $1 million hacker challenge for Vercel Sandbox DevFeed: [$1 million hacker challenge for Vercel Sandbox]() Original publisher: [Read original article]() Author: Andy Riancho Published: 2026-08-18T13:00:00Z Content type: article Language: en Sources: [Vercel News]() Topics: [Vercel](), [Firecracker](), [Security](), [vulnerability](), [Network](), [Amazon EC2](), [Linux](), [Open Source]() Tags: [agents](), [bounty](), [firecracker](), [linux](), [network](), [open-source](), [sandbox](), [security](), [vercel](), [vulnerability]() ### AI overview Vercel announces a two-week public HackerOne challenge offering up to $1 million in total payouts for researchers who can escape Vercel Sandbox isolation. The article explains that Sandbox uses Firecracker microVMs on bare-metal Amazon EC2 hosts, with host-side network controls forming part of the security boundary. Individual reports can receive up to $50,000 for vulnerabilities allowing access to another Vercel tenant's data. ### Source excerpt Agents need to run untrusted code, and the microVM has become the standard way to do it: a dedicated guest kernel per workload, isolated from the host and from every other workload on the same machine. But recent security research and real-world incidents have revealed that agents running untrusted code do not need to cross a VM boundary to escape containment; they only need one network path the security model failed to account for, which we explained in our post A sandbox without a network boundary is only half a sandbox. Isolation only holds if both sides of it hold: the Firecracker microVM and the host-side network controls. Recently our CTO pointed an open-weight model with no safeguards at Vercel Sandbox. It did not escape, but it mapped the guest kernel, built a VM to reproduce its ideas, and wrote a fuzzer. Defenders have first-mover advantage, but it won't last forever, and the choice is when to test the boundaries (we strongly encourage building a scanning program, which you can do on any budget with an open-source tool like deepsec and AI Gateway). We are proactively choosing to test Vercel Sandbox on our own schedule, not an attacker's, and we are doing it in the open, with the best researchers in the world. So for two weeks, we are paying up to $1,000,000 USD to the researchers who can escape a Vercel Sandbox. The challenge Starting today, Vercel is running a two-week public HackerOne program focused on Vercel Sandbox isolation. Program: Public HackerOne program, open to all eligible researchers Window: Tuesday, August 18 to Tuesday, September 1, 2026, or earlier if the reward pool is exhausted Max per report: $50,000 USD, for a vulnerability that lets a threat actor read or modify another Vercel tenant's data Total pool: Up to $1,000,000 USD in total payouts Bounties are paid per report, scoped to a single root cause, and assigned by Vercel triage based on the maximum demonstrable impact. The full bounty table, detailed scope, and the list of known-dupl ## AWS Weekly Roundup: EC2 application status checks, IAM role manager, OpenAI Daybreak on Bedrock, and more (August 17, 2026) DevFeed: [AWS Weekly Roundup: EC2 application status checks, IAM role manager, OpenAI Daybreak on Bedrock, and more (August 17, 2026)]() Original publisher: [Read original article]() Author: Channy Yun (윤석찬) Published: 2026-08-17T16:02:36Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [Amazon Web Services](), [Amazon EC2](), [AWS IAM](), [Amazon OpenSearch Service](), [Open Source](), [Amazon Bedrock](), [Linux](), [OpenAI](), [MCP]() Tags: [amazon-bedrock](), [amazon-ec2](), [amazon-elasticache](), [amazon-opensearch-service](), [amazon-sagemaker-jumpstart](), [aws](), [aws-certificate-manager](), [aws-client-vpn](), [aws-identity-and-access-management-iam](), [bedrock](), [iam](), [linux](), [mcp](), [news](), [open-source](), [openai](), [oracle-database-aws](), [week-in-review]() ### AI overview AWS Weekly Roundup highlights EC2 application status checks, automatic IAM role setup, OpenAI Daybreak on Amazon Bedrock, and updates involving OpenSearch, Valkey, and open source community events. ### Source excerpt Last week, AWS contributors joined the OpenSearch and Valkey communities at Open Source Summit Korea 2026 and MCP DevSummit Seoul 2026 to meet open source developers and contributors. At the four-day event, community leaders and users of these Linux Foundation open source projects gathered to share knowledge, collaborate on solutions, and push the projects forward. [...] ## Burst to Region: Overflow AWS Outposts workloads to Amazon EC2 DevFeed: [Burst to Region: Overflow AWS Outposts workloads to Amazon EC2]() Original publisher: [Read original article]() Author: Diya Published: 2026-08-12T17:06:54Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [Amazon EC2](), [Amazon Web Services](), [datacenter](), [Latency](), [Availability](), [Amazon CloudWatch](), [AWS Lambda](), [Cloud]() Tags: [advanced-300](), [amazon-cloudwatch](), [amazon-ec2](), [api](), [applications](), [availability](), [aws](), [aws-lambda](), [aws-outposts](), [cloud](), [compute](), [data-center](), [infrastructure](), [latency](), [technical-how-to]() ### AI overview This tutorial presents a Burst to Region pattern for AWS Outposts workloads. When an Outposts rack reaches its fixed compute capacity, the pattern launches Amazon EC2 instances in the parent AWS Region, shifts traffic gradually, and returns traffic to local instances when capacity recovers. It uses CloudWatch, SNS, Lambda, EC2 Auto Scaling, Elastic Load Balancing, and EventBridge, trading increased latency for continued availability during capacity events. ### Source excerpt AWS Outposts brings AWS infrastructure into your data center with low latency and data locality. But an Outposts rack has fixed compute. Learn how to build a Burst to Region pattern that overflows workloads to Amazon EC2 in the parent Region when local capacity is exhausted. ## Runtime instances: persistent compute for production AI agents on Amazon Bedrock AgentCore DevFeed: [Runtime instances: persistent compute for production AI agents on Amazon Bedrock AgentCore]() Original publisher: [Read original article]() Author: Sébastien Stormacq Published: 2026-08-06T22:58:00Z Content type: release Language: en Sources: [AWS News Blog]() Topics: [Amazon Bedrock](), [Artificial Intelligence](), [Amazon EC2](), [Amazon Web Services](), [GPU](), [observability]() Tags: [agents](), [ai](), [ai-agents](), [amazon](), [amazon-bedrock](), [amazon-bedrock-agentcore](), [apis](), [aws](), [bedrock](), [compute](), [developers](), [framework](), [infrastructure](), [launch](), [memory](), [model](), [monitoring](), [news](), [os](), [production](), [storage](), [tools]() ### AI overview Amazon Bedrock AgentCore runtime instances provide persistent, AWS-managed EC2 infrastructure for production AI agents. The feature supports multi-agent collaboration, shared sessions lasting up to 14 days, GPU acceleration, containerized deployments, session stop/restart, and integration with EBS, AgentCore Memory, existing APIs, identity controls, and observability. ### Source excerpt Announcing runtime instances in Amazon Bedrock AgentCore--persistent, managed EC2 infrastructure for production AI agents with multi-agent collaboration, GPU support, and sessions lasting up to 14 days. ## What is WAL backpressure, and why does ClickHouse Managed Postgres need it? DevFeed: [What is WAL backpressure, and why does ClickHouse Managed Postgres need it?]() Original publisher: [Read original article]() Author: Kaushik Iska Published: 2026-08-05T15:58:59Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Database](), [systemd](), [Amazon EC2](), [benchmarking](), [Processes](), [Ubuntu]() Tags: [backend](), [benchmark](), [clickhouse](), [database](), [process](), [scale](), [storage](), [systemd](), [ubuntu]() ### AI overview ClickHouse Managed Postgres uses WAL-aware backpressure to prevent a full WAL disk from causing an outage. A systemd timer measures pending WAL segments and applies increasingly strict cgroup v2 I/O limits to client backends while leaving the archiver, checkpointer, logger, and all reads uncapped. A benchmark on an EC2 instance demonstrates the mechanism under a deliberately rate-limited object store and a backed-up archiver. ### Source excerpt How ClickHouse Managed Postgres uses WAL-aware backpressure to slow client writes, protect disk space, and let the archiver recover. ## On building scalable control planes DevFeed: [On building scalable control planes]() Original publisher: [Read original article]() Author: werner@allthingsdistributed.com (Dr. Werner Vogels) Published: 2026-08-04T14:00:00Z Content type: article Language: en Sources: [All Things Distributed]() Topics: [distributed-systems](), [Amazon Web Services](), [Amazon EC2](), [DSQL](), [Cloud]() Tags: [aws](), [cloud](), [distributed-systems](), [dsql](), [infrastructure](), [kubernetes](), [posts](), [servers](), [ssh]() ### AI overview This article explores the engineering of scalable control planes through Zak van der Merwe's experience building them at AWS, first for EC2 and later for DSQL. It explains how control planes record intended state and reconcile it with actual state, bringing together difficult distributed-systems problems and influencing whether services can survive growth. ### Source excerpt Zak van der Merwe has spent his entire career at AWS building control planes. First for EC2 and now for DSQL. On the surface, the control plane looks quite boring: it records what should exist and reconciles that with what actually does. Nobody leaves school dreaming of building one, but Zak will be the first to tell you that if you like solving hard problems in distributed systems, there are few better places to be. It's where many of those hard problems converge, and where the decisions you make determine whether a service survives its own growth. ## Cloud Cost Visibility at Scale: Best Practices DevFeed: [Cloud Cost Visibility at Scale: Best Practices]() Original publisher: [Read original article]() Author: Kelsey Rosen Published: 2026-08-04T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Cloud](), [finops](), [cloud cost management](), [Amazon Web Services](), [Amazon EC2](), [Amazon S3](), [Kubernetes](), [Microservice]() Tags: [aws](), [best-practices](), [cloud](), [cloud-cost-management](), [ec2](), [finops](), [how-to](), [kubernetes](), [microservices](), [s3]() ### AI overview The article explains why cloud cost visibility and allocation practices break down as organizations scale across accounts, teams, services, and workloads. It argues that periodic reporting, manual reviews, and static tagging models become ineffective, and highlights FinOps governance and automation as ways to improve control and trust in cost data. ### Source excerpt Discover why cloud cost visibility at scale breaks down and how to regain control. Learn proven FinOps strategies. Explore now. | Blog ## I created a playground for 110 database systems DevFeed: [I created a playground for 110 database systems]() Original publisher: [Read original article]() Author: Alexey Milovidov Published: 2026-08-03T08:32:12Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [Database](), [Amazon EC2]() Tags: [automation](), [benchmark](), [clickhouse](), [database](), [playground]() ### AI overview A developer describes an interactive playground for testing and comparing 110 database systems, built from the ClickBench benchmarking project. ### Source excerpt You can choose any of these hundred database systems and run queries. You can create tables and databases, insert data, drop tables, etc. Every database comes with a preloaded dataset of 100 million records, so you can test example queries. It has not onl ## Asynchronous I/O in DuckDB: Work, Thread, Work DevFeed: [Asynchronous I/O in DuckDB: Work, Thread, Work]() Original publisher: [Read original article]() Author: {"picture" =\> "/images/blog/authors/pedro\_holanda.jpg"} Published: 2026-07-31T00:00:00Z Content type: article Language: en Sources: [DuckDB]() Topics: [aio](), [CSV](), [Amazon S3](), [Amazon EC2]() Tags: [deep-dive](), [duckdb](), [latency](), [parquet](), [performance](), [s3]() ### AI overview DuckDB v2.0 will add asynchronous reads for Parquet and CSV files to improve query performance when remote I/O cannot saturate available bandwidth. The article contrasts local SSD workloads with remote data-lake setups using S3 and EC2, where concurrent reads can keep worker threads from waiting on network requests. ### Source excerpt Starting with v2.0, scheduled for fall 2026, DuckDB will support asynchronous reads of Parquet and CSV files. This can significantly speed up queries when synchronous I/O does not saturate the available bandwidth, as is typical in EC2/S3 compute-storage setups. ## AWS Weekly Roundup: Local Zone in Athens, Claude Opus 5 on AWS, Lambda durable execution for .NET, and more (July 27, 2026) DevFeed: [AWS Weekly Roundup: Local Zone in Athens, Claude Opus 5 on AWS, Lambda durable execution for .NET, and more (July 27, 2026)]() Original publisher: [Read original article]() Author: Daniel Abib Published: 2026-07-27T14:54:41Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [Amazon Web Services](), [AWS Local Zones](), [Latency](), [Amazon Bedrock](), [Amazon EC2](), [Amazon S3](), [Claude](), [cloud-infrastructure](), [Amazon Elastic Container Service](), [anthropic](), [data-governance]() Tags: [amazon-bedrock](), [amazon-bedrock-agentcore](), [amazon-connect](), [amazon-ec2](), [amazon-s3](), [amazon-sagemaker-ai](), [announcements](), [anthropic](), [aws](), [aws-lambda](), [aws-local-zones](), [claude](), [data-governance](), [latency](), [news](), [week-in-review]() ### AI overview An AWS weekly roundup covering a new Local Zone in Athens, Greece, and selected AWS launches and updates, including Claude Opus 5 on Amazon Bedrock. The article highlights local data processing, data residency, low latency, and infrastructure for regional workloads. ### Source excerpt Last week I had the privilege of spending three days in São Paulo with technical builders from across Latin America, brought together for a regional tech event full of deep-dive sessions, hands-on workshops, and conversations with customers and partners. What struck me most wasn't any single session, it was the energy of a technical community [...] [Next page]()