Posts

Amazon EKS now supports EFA and placement groups on Amazon EKS Auto Mode and Karpenter - devamazonaws.blogspot.com

Amazon Elastic Kubernetes Service (EKS) now supports Amazon EC2 placement groups and Elastic Fabric Adapter (EFA) network device configuration for node pools on EKS Auto Mode and the open-source Karpenter project, enabling you to optimize EKS workloads for performance and availability. These capabilities allow you to control EFA network interface configuration and how EC2 instances are physically distributed across AWS infrastructure for distributed training and inference workloads. With EKS Auto Mode and Karpenter’s EFA configuration, you can configure network interfaces as EFA-only or standard ENI on EFA-capable instances with both dynamic and static capacity node pools. EFA-only interfaces do not consume IP addresses, giving you fine-grained control over IP utilization in your VPC while achieving full interconnect bandwidth. With placement group support, you can launch EC2 instances using cluster, spread, or partition strategies directly from your EKS Auto Mode or Karpenter node p...

AWS Elastic Disaster Recovery is now available in six additional AWS Regions - devamazonaws.blogspot.com

AWS Elastic Disaster Recovery (AWS DRS) is now available in six additional AWS Regions: Asia Pacific (Bangkok), Asia Pacific (Malaysia), Asia Pacific (New Zealand), Asia Pacific (Taipei), Canada West (Calgary), and Mexico (Central). Elastic Disaster Recovery is the recommended service for disaster recovery to AWS. It helps minimize downtime and data loss with fast, reliable recovery of on-premises and cloud-based applications using affordable storage, minimal compute, and point-in-time recovery. With Elastic Disaster Recovery, you can recover your applications on AWS from physical infrastructure, VMware vSphere, Microsoft Hyper-V, and cloud infrastructure. You can also use Elastic Disaster Recovery to recover Amazon EC2 instances in a different AWS Region. AWS DRS replicates and recovers a wide range of applications, including critical databases such as Oracle, MySQL, and SQL Server, and enterprise applications such as SAP. AWS DRS uses a unified process for drills, recovery, and failb...

[MS] The Microsoft Agent Framework Harness is now released - devamazonaws.blogspot.com

Image
Your agents can now be built on a stable, batteries-included harness - the loop, planning, memory, context management, approvals, and telemetry that turn a model into an agent that actually does things - in both Python and .NET . What is an agent harness? An agent harness is the scaffolding that turns a language model into an agent. A model on its own can only generate text. To have it call tools, work through multi-step tasks, remember what it has done, and keep going until the job is finished, you need a runtime wrapped around the model - and that runtime is the harness. Agent Framework ships a ready-made one so you don't have to build that scaffolding yourself. It's an opinionated, fully customizable, batteries-included agent that wraps a chat client with a complete agentic pipeline, tuned for long-running, autonomous work such as research, data analysis, and general task automation. Internally it's just a chat-client agent ( Agent in Python, ChatClientAgent in ....

Amazon ECS advanced deployment strategies now available in AWS European Sovereign Cloud - devamazonaws.blogspot.com

Amazon Elastic Container Service (Amazon ECS) now supports built-in blue/green, linear, and canary deployment strategies in the AWS European Sovereign Cloud, making software updates for containerized applications safer and allowing you to release new application versions faster with greater confidence. Built directly into Amazon ECS, these capabilities eliminate the need for custom deployment tooling while providing production-ready controls including deployment lifecycle hooks, bake time, and quick rollback. With these strategies, Amazon ECS provisions a new application version alongside the existing version and allows you to validate it before shifting production traffic. Blue/green deployments shift traffic in a single step, linear deployments shift traffic in equal increments over a specified period, and canary deployments shift a small percentage initially before shifting the remainder. You can use deployment lifecycle hooks, including Lambda hooks and pause hooks, to run custo...

[MS] Display Name is for Humans - devamazonaws.blogspot.com

Package identity exists for one primary purpose: To provide software with a stable and unambiguous way to identify a package. This is a considerable improvement over the historical tendency to assign UUIDs and GUIDs to nearly everything - including things that humans were expected to discuss in meetings. Identity Is for Systems A package's Name , Package Full Name , and other identity-derived values are intended for developer and system use. These identifiers prioritize correctness, uniqueness, and programmatic consumption - not clarity or friendliness from an end-user's perspective. Identity must remain stable across servicing operations and dependency resolution. If it changes, the system quite reasonably concludes that it is no longer the same package. DisplayName Is for Humans That's where DisplayName comes in. People use a package's display name. You'll typically see it in Start, Settings, installation experiences, and runtime surfaces. ...

[MS] Pure Virtual C++ 2026 Is Now Live! - devamazonaws.blogspot.com

Image
Pure Virtual C++ 2026, our free, one-day virtual conference for the whole C++ community, is live right now! Join hosts Mads Kristensen and Sinem Akinci for three hours of featured sessions, and real-time Q&A in the chat. Watch live now → streaming on YouTube (Microsoft Reactor channel) and Twitch. Bring your curiosity and your questions! Our hosts and speakers are in the live chat, so this is a chance to interact with the speakers directly. Today's live schedule The broadcast starts now . Here's the schedule: Time (PT) Session Speaker 9:00 AM Welcome & opening Mads Kristensen, Sinem Akinci 9:00 AM C++ semantic awareness in the CLI: From Project Load to Code Change Sinem Akinci 9:20 AM Mind The Gap: C++/Rust Interop Victor Ciura 9:45 AM From Completions to Agents: AI-Driven C++ in Visual Studio Augustin Popa 10:25 AM Cut Your Build Times Without Becoming a Build Expert David Li 10:40 AM C++/WinRT: Build faster and smaller with...

[MS] How to test agent experience changes without shipping them - devamazonaws.blogspot.com

You've built an eval. You've established a baseline and found the gaps. Now you have hypotheses about how to fix them: maybe a documentation rewrite, or a different CLI output format. The natural next step is to ship the change and measure again. Don't do that just yet. Why most hypotheses fail Every improvement you think of is a hypothesis. "If I add a warning callout to the release notes, the agent will use the CLI instead of attempting a manual upgrade." It sounds reasonable, might even be obvious. But LLMs don't reason the way you expect them to, and obvious changes produce counterintuitive results with uncomfortable regularity. We've seen this first-hand working on a SharePoint Framework (SPFx) project upgrade scenario. SPFx projects upgrade incrementally, version by version, each step introducing its own configuration- and dependency changes. The agent needed to discover a CLI tool from documentation. The documentation included a tip recommend...