# Amazon EC2 Published articles for Amazon EC2. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## Building resilient real-time streaming workers with Amazon DynamoDB leases DevFeed: [Building resilient real-time streaming workers with Amazon DynamoDB leases]() Original publisher: [Read original article]() Author: Siddhesh Tiwari Published: 2026-09-10T16:14:22Z Content type: tutorial Language: en Sources: [AWS Architecture Blog]() Topics: [WebSocket](), [Amazon EC2](), [Amazon Elastic Kubernetes Service]() Tags: [advanced-300](), [amazon-dynamodb](), [amazon-ec2](), [amazon-eks](), [amazon-elastic-container-service](), [aws-fargate](), [how-to](), [real-time](), [streaming](), [technical-how-to](), [workers]() ### AI overview A tutorial for building resilient real-time WebSocket workers with Amazon DynamoDB leases. It covers conditional-write ownership, orphan reconciliation for automatic failover, and graceful shutdown to reduce deployment downtime on Amazon ECS and AWS Fargate. ### Source excerpt Real-time streaming workers that hold hundreds of persistent WebSocket connections lose data when a worker fails. Learn how to build a WebSocket fleet management system on Amazon ECS and AWS Fargate that uses Amazon DynamoDB conditional writes as a distributed lease to track ownership, fail over automatically, and deploy with low downtime. ## 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. ## AWS Weekly Roundup: Welcome DuckLabs to the team, Agentic Resource Discovery (ARD), and more (August 31, 2026) DevFeed: [AWS Weekly Roundup: Welcome DuckLabs to the team, Agentic Resource Discovery (ARD), and more (August 31, 2026)]() Original publisher: [Read original article]() Author: Daniel Abib Published: 2026-08-31T14:45:25Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [data](), [Amazon S3](), [Amazon Redshift](), [Node.js]() Tags: [acquisition](), [amazon-ec2](), [amazon-elastic-container-service](), [amazon-gamelift](), [amazon-redshift](), [amazon-s3](), [amazon-sagemaker](), [amazon-sagemaker-ai](), [analytics](), [announcements](), [aws](), [aws-fargate](), [aws-glue](), [aws-iot-core](), [aws-lambda](), [database](), [duckdb](), [json](), [news](), [node-js](), [open-source](), [parquet](), [python](), [sql](), [week-in-review]() ### AI overview AWS weekly roundup covering the planned acquisition of DuckLabs, the company behind DuckDB, alongside Amazon ECS recovery updates and AWS Lambda preview runtimes for Node.js 26 and Python 3.15. ### Source excerpt The news that interested me the most last week was the DuckLabs acquisition. AWS has signed a definitive agreement to acquire DuckLabs, the Amsterdam-based company behind DuckDB, the popular open source analytical database that runs in-process and executes SQL directly against files like Parquet, CSV, and JSON. DuckDB stays open source under its independent foundation [...] ## 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. ## 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. ## Characterizing SQL\*Net latency in your application for Oracle Database@AWS migrations DevFeed: [Characterizing SQL\*Net latency in your application for Oracle Database@AWS migrations]() Original publisher: [Read original article]() Author: Sameer Malik Published: 2026-08-18T18:17:28Z Content type: article Language: en Sources: [AWS Database Blog]() Topics: [Oracle Database](), [Latency](), [migration](), [Amazon Web Services](), [Database](), [Network]() Tags: [advanced-300](), [amazon-ec2](), [amazon-elastic-container-service](), [amazon-elastic-kubernetes-service](), [amazon-vpc](), [aws](), [best-practices](), [database](), [latency](), [migration](), [network](), [oracle](), [oracle-database-aws](), [performance]() ### AI overview This article presents a methodology for assessing SQL*Net latency sensitivity before migrating Oracle workloads to Oracle Database@AWS. It focuses on identifying workloads with fast, frequent, and concentrated SQL activity, then quantifying the impact of added network round-trip latency in a multi-cloud architecture. It also discusses reducing client-server round trips through stored procedures, array fetches, and bulk processing. ### Source excerpt Oracle Database@AWS places Oracle Exadata infrastructure inside AWS data centers, so SQL*Net latency between your application and the database can change after migration. This post presents the CRET methodology, a three-phase approach using AWR, Active Session History, and SQL Trace, to identify latency-sensitive SQL and quantify the impact before you migrate. ## 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. [...] ## Designing for failure: Building resilient systems on AWS DevFeed: [Designing for failure: Building resilient systems on AWS]() Original publisher: [Read original article]() Author: Dhvani Vora Published: 2026-08-13T20:03:28Z Content type: tutorial Language: en Sources: [AWS Compute Blog]() Topics: [incident](), [Incident response]() Tags: [amazon-ec2](), [aws](), [aws-architecture-blog-resilience](), [aws-management-tools-blog-aws-resilience-hub](), [best-practices](), [cassandra](), [distributed-systems](), [hardware](), [incident](), [intermediate-200](), [kafka](), [observability](), [resilience](), [systems]() ### AI overview An AWS resilience guide examines a correlated EC2 hardware failure that took down three colocated Cassandra nodes. It covers placement groups, alarms, automated recovery, and observability patterns for distributed data systems. ### Source excerpt Learn how to prevent correlated hardware failures in distributed systems on Amazon EC2. This post walks through real incident response patterns, including Partition Placement Groups, composite alarms, automated recovery with Auto Scaling, and observability best practices. ## 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. ## 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 [...] ## Architecting for IOPS and throughput performance on AWS Outposts racks DevFeed: [Architecting for IOPS and throughput performance on AWS Outposts racks]() Original publisher: [Read original article]() Author: Brianna Rosentrater Published: 2026-07-10T17:10:39Z Content type: article Language: en Sources: [AWS Compute Blog]() Topics: [AWS Outposts](), [Amazon EC2](), [cloud-infrastructure](), [Latency](), [data-processing]() Tags: [amazon-ec2](), [aws](), [aws-outposts](), [cloud](), [compute](), [infrastructure](), [latency](), [low-latency](), [performance](), [post]() ### AI overview This article explains how to design AWS Outposts rack deployments for target IOPS and throughput. It examines the performance limits of EC2 instances and attached EBS volumes, and provides guidance for sizing instances and storage. ### Source excerpt AWS Outposts extend AWS infrastructure, services, APIs, and tools to on-premises locations for workloads that require low latency, local data processing, or data residency. In this post, you learn how to configure instances running on an Outpost to support the required IOPS and throughput for your application. The actual IOPS available to an instance is [...] ## AWS Weekly Roundup: Claude Sonnet 5 on AWS, Amazon WorkSpaces for AI agents, AWS service availability updates, and more (July 6, 2026) DevFeed: [AWS Weekly Roundup: Claude Sonnet 5 on AWS, Amazon WorkSpaces for AI agents, AWS service availability updates, and more (July 6, 2026)]() Original publisher: [Read original article]() Author: Daniel Abib Published: 2026-07-06T15:46:43Z Content type: news Language: en Sources: [AWS News Blog]() Topics: [Amazon WorkSpaces](), [Amazon EC2](), [AWS CloudFormation](), [Amazon Elastic Kubernetes Service](), [Kubernetes]() Tags: [ai-agents](), [amazon-bedrock](), [amazon-cloudwatch](), [amazon-ec2](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [amazon-opensearch-service](), [amazon-sagemaker-ai](), [amazon-workspaces](), [aws](), [aws-certificate-manager](), [aws-cloudformation](), [claude](), [kubernetes](), [news](), [tls](), [week-in-review]() ### AI overview AWS weekly roundup covering Amazon WorkSpaces for AI agents, Claude Sonnet 5 availability, service availability updates, and recent launches including EC2 instances, CloudFormation Express mode, EKS Kubernetes rollbacks, and ACM ACME support. ### Source excerpt A couple of editions ago I wrote about what I find so energizing about working with startups. Last week I got a fresh dose of it: I spent a few days with the AWS Startups team, listening to stories of founders talking about the problems they're actually solving. One story that stayed with me came [...] ## How AWS Powers Gradle's Open Source Build Tool DevFeed: [How AWS Powers Gradle's Open Source Build Tool]() Original publisher: [Read original article]() Author: Bo Zhang Published: 2026-06-09T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Amazon Web Services](), [ci](), [Testing](), [Open Source](), [Security](), [AWS IAM](), [Amazon EC2](), [Amazon Elastic Kubernetes Service](), [Amazon S3](), [OpenID connect (OIDC)]() Tags: [amazon-ec2](), [amazon-eks](), [amazon-rds](), [aws](), [aws-identity-and-access-management-iam](), [ci](), [gradle](), [oidc](), [open-source](), [security](), [testing]() ### AI overview The article explains how AWS supports Gradle's open source build tool, including plugin distribution through Amazon S3, large-scale builds and tests on Amazon EC2 and Amazon EKS, performance tracking with Amazon RDS, and layered security and observability services. ### Source excerpt The Gradle Build Tool runs a lot of the world's software. Millions of developers use it every day, and almost every Android app on your phone was built with it. So somebody, somewhere, is kicking off a Gradle build right now. And the next one. And a thousand more in the next minute. For all of them, it has to be fast, and it has to be there. That isn't free. Behind the open source project sits a plugin portal serving hundreds of millions of downloads a month, a CI fleet running millions of tests, a performance lab watching for regressions, and the security tooling that guards a supply chain a lot of the industry depends on. All of it runs on AWS. Here's how. Downloading plugins The Gradle Plugin Portal at plugins.gradle.org is where the community publishes the plugins that extend Gradle. Every plugin JAR it serves (thousands of them, downloaded around 200 million times a month) lives in Amazon S3. That's what lets us be the front door for the plugin ecosystem without running a fleet of file servers ourselves. Building and testing Gradle itself Most of our AWS bill goes here. Every commit to Gradle triggers hundreds of separate builds and tens of thousands of tests across our supported operating systems and architectures. That fleet runs on: Amazon EC2, with auto-scaling to match capacity to demand. Amazon EKS, which orchestrates our containerized Test Distribution agents. Amazon ECR, which stores the agent container images. Keeping Gradle fast A build tool only earns trust if it stays fast. Every commit runs through our performance test suite, and the results land in Amazon RDS, where we compare against history and catch regressions before they reach users. Securing the build Protecting a build tool means protecting a supply chain. Our CI authenticates to AWS through AWS Identity and Access Management (IAM) with GitHub OIDC. That gives us keyless, short-lived credentials, and any secrets we still need are pulled on demand from AWS Secrets Manager and AWS Systems Man ## AWS and OpenAI announce multi-year strategic partnership DevFeed: [AWS and OpenAI announce multi-year strategic partnership]() Original publisher: [Read original article]() Published: 2025-11-03T06:00:00Z Content type: news Language: en Sources: [OpenAI News]() Topics: [Amazon Web Services](), [OpenAI](), [AI Infrastructure](), [cloud-infrastructure](), [Cloud](), [Generative AI](), [AWS AI chips](), [Amazon EC2](), [Inference](), [Low Latency]() Tags: [ai](), [ai-infrastructure](), [amazon-ec2](), [announce](), [artificial-intelligence](), [aws](), [capacity](), [cloud](), [cloud-infrastructure](), [company](), [compute](), [generative-ai](), [growth](), [inference](), [infrastructure](), [latency](), [leadership](), [models](), [openai](), [partnership](), [scale]() ### AI overview AWS and OpenAI announced a multi-year strategic partnership valued at $38 billion. AWS will provide large-scale infrastructure, including NVIDIA GPU clusters and Amazon EC2 UltraServers, to support OpenAI's generative AI workloads, inference for ChatGPT, and training of next-generation models. ### Source excerpt OpenAI and AWS have entered a multi-year, $38 billion partnership to scale advanced AI workloads. AWS will provide world-class infrastructure and compute capacity to power OpenAI's next generation of models. ## How a major retailer tested critical serverless systems with Failure Flags DevFeed: [How a major retailer tested critical serverless systems with Failure Flags]() Original publisher: [Read original article]() Author: Gavin Cahill Published: 2025-03-12T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [Failure Flags](), [AWS Lambda](), [Serverless](), [systems](), [Amazon EC2](), [Amazon Web Services]() Tags: [amazon-ec2](), [aws-lambda](), [failover](), [failure-flags](), [gremlin](), [infrastructure](), [outage](), [serverless](), [testing]() ### AI overview A case study describes how a major apparel retailer used Gremlin Failure Flags to test regional failover for a critical payment service built on AWS Lambda. Because Lambda abstracts the underlying infrastructure, conventional infrastructure-level fault injection could not reproduce a regional failure. Failure Flags enabled the retailer to run the failover test in less than 30 minutes. ### Source excerpt Find out how Gremlin helped a major retailer test region failover for a critical service built on AWS Lambda using Failure Flags. ## Maximizing your reliability on AWS DevFeed: [Maximizing your reliability on AWS]() Original publisher: [Read original article]() Author: Andre Newman Published: 2025-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Gremlin Blog]() Topics: [Amazon Web Services](), [Shared Responsibility Model](), [Amazon EC2](), [Availability](), [cloud-infrastructure](), [Amazon Elastic Kubernetes Service](), [App]() Tags: [amazon](), [amazon-ec2](), [availability](), [aws](), [cloud](), [compute](), [how-to](), [infrastructure](), [learn](), [shared-responsibility-model](), [use-cases]() ### AI overview This article explains how to improve workload reliability on AWS despite the cloud platform's limited visibility and shared responsibility model. It examines failure modes and mitigation options for services including Amazon EC2, Amazon EKS, and ECS, with emphasis on resilience, recoverability, fault tolerance, and EC2 auto-scaling groups. ### Source excerpt Learn how to maximize reliability when running workloads on Amazon EC2, EKS, ECS, and other services. ## Ten Years of AWS Lambda DevFeed: [Ten Years of AWS Lambda]() Original publisher: [Read original article]() Author: Marc Brooker Published: 2024-11-14T00:00:00Z Content type: article Language: en Sources: [Marc Brooker's Blog](), [Marc Brooker's Blog]() Topics: [AWS Lambda](), [Serverless](), [npm](), [Dependency management](), [Go Language](), [Rust](), [C++](), [Amazon EC2]() Tags: [amazon-ec2](), [aws-lambda](), [c-plus-plus](), [dependencies](), [go](), [npm](), [rust](), [serverless]() ### AI overview The article reflects on AWS Lambda's ten-year development, focusing on its initial Node.js launch, npm-based dependency packaging, later Go support, and the introduction of custom runtimes. It also discusses language packaging challenges and compares Lambda latency with earlier EC2 experience. ### Source excerpt Ten Years of AWS Lambda Everything starts somewhere. Today, Werner Vogels shared his annotated version of the original AWS Lambda PRFAQ. This is a great inside look into how product development happens at AWS - the real working backwards process in action. This was, in some ways, the start of serverless computing2. Tim Wagner, Ajay Nair, and others really saw the future when they wrote this PRFAQ3. I wanted to take the opportunity to dive a little deeper into some of the things Werner highlights. We made the hard decision to only launch with support for Node, which was popular at the time Another thing Node had going for it in 2014 was a great dependency management story (via npm). It's really easy to zip up a NodeJS program along with its dependencies into a nice self-contained unit, without changing anything about the developer flow. This makes NodeJS my go-to for developing small Lambda functions to this day. It's really this easy: zip -r function.zip index.mjs node_modules Over time, languages like Go and Rust, which are mostly statically linked have made this easy for binary programs too, but those languages weren't very well known a decade ago. C and C++ remain rather difficult to package up, given their rather deep ties into the OS userland, and we had to wait for container support to do a great job there. Go support (Jan 2018) Custom Runtimes (Nov 2018) A few days ago, I did an episode of the AWS developer podcast where I talked about some of the surprises that came as we built the Lambda business. Custom runtimes was one of those. We knew that customers wanted more flexibility around languages, but we also thought that wrapping custom code in little NodeJS or Python scripts wasn't too onerous. The launch of Go support, which was really custom runtime support under the covers, opened the flood gates of customers doing interesting and cool things to bring their own languages (C++, Rust, different JVMs, etc), and made it super clear to us that we needed offici [Next page]()