Posts

Amazon CloudWatch Omni: AI-first observability for agents and applications - devamazonaws.blogspot.com

AWS announces the general availability of Amazon CloudWatch Omni, an evolution of Amazon CloudWatch. Omni is an AI-powered observability experience organized around your teams and the applications they run, so that you can observe and troubleshoot your applications and agents in one place. It combines the interoperability of OpenTelemetry with the scale and reliability of CloudWatch. And it meets you wherever you work: a standalone web experience with single sign-on (SSO) for your team, or a local IDE extension for getting hands-on with your agents. With CloudWatch Omni, you create spaces in your central accounts to see telemetry across your AWS accounts and Regions, as well as other clouds, including Azure workloads. Omni automatically discovers services, maps dependencies, and surfaces golden metrics to help streamline your operational workflows. Using Omni, you can interact with telemetry however you prefer: via chat, through a guided point-and-click path in the console, or directl...

Amazon EMR 7.14 is now available - devamazonaws.blogspot.com

Amazon EMR 7.14 is now available with new features across Amazon EMR on EC2, Amazon EMR on EKS, and Amazon EMR Serverless, along with version upgrades for additional applications. This release also upgrades Apache Spark to 3.5.8 and Apache Iceberg to 1.10.1. Apache Iceberg materialized views now refresh faster on tables with updates and deletes, using change data capture to read only the data files affected by a change. On Amazon EMR on EKS, clusters now support Spark Connect endpoints for interactive Spark sessions with token-based authentication, and can run workloads on IPv6 Amazon EKS clusters. On Amazon EMR Serverless, the storage limit for Spark jobs increases from 200 GiB to 1 TiB, giving more room for shuffle data. Amazon EMR 7.14 is available in all AWS Regions where Amazon EMR is available. To learn more, visit the Amazon EMR 7.14 Release Guide , or get started by creating a cluster from the Amazon EMR console . Post Updated on September 22, 2026 at 09:00AM

[MS] Faster C++ code intelligence for Copilot CLI with Whole Codebase Indexing - devamazonaws.blogspot.com

C++ repositories can contain millions of lines of code spread across deeply connected source files and headers. Without a reusable index, navigating to definitions, finding references, or searching for symbols may require portions of that information to be analyzed again as you move through the repository. C++ code intelligence in GitHub Copilot CLI is now faster with support for Whole Codebase Indexing (WCI) . Powered by the Microsoft C++ Language Server , WCI uses your project’s compilation information to maintain a persistent index of symbols and relationships across source files and headers, allowing Copilot CLI to understand the codebase without repeatedly parsing it from scratch. Because the index runs directly within the CLI experience, an IDE does not need to be open to establish or maintain project understanding. Copilot CLI can use indexed declarations, definitions, references, implementations, includes, and type relationships when tracing call paths, assessing the impact o...

[MS] Using Azure Blob Storage as a durable filesystem for LangChain Deep Agents - devamazonaws.blogspot.com

Image
LangChain Deep Agents is an open-source agent harness with built-in capabilities for building LLM-powered agents and applications, including complex, multi-step workflows. A model can reason and generate responses, but it needs a harness to do useful work over time. The harness provides the tools and runtime that let the model retrieve the right context, take actions, and manage work across multiple steps. Deep Agents supplies that structure through planning, context management, a virtual filesystem, memory and skills, specialized subagents, and human approval points. Filesystems give agents a familiar way to organize and work with context. An agent can list and search files, read only what the current task needs, update artifacts, keep notes, and share work with subagents. This makes the filesystem useful as both a workspace and external memory for long-running tasks, a pattern LangChain highlights in its Deep Agents architecture . Deep Agents exposes this pattern through tools fo...

[MS] Foundry hosted agent isolation with Microsoft Agent Framework - devamazonaws.blogspot.com

Foundry hosted agent isolation exposes two independent controls. User isolation identifies whose data may be used . At the same time, Foundry hosted session isolation identifies where code and files continue to live . For each control, Foundry can resolve the value or the application can provide it. Therefore, the available choices support direct callers, trusted middle tiers, application-managed sessions, and shared session pools. While Foundry hosted agents are generally available in Microsoft Foundry, the AgentServer SDKs and the Microsoft Agent Framework Foundry hosting packages for .NET and Python are still in pre-release versions. Foundry hosted agent isolation controls Control Represents Available choices User isolation The user represented by the current request The caller's Microsoft Entra identity, or a delegated identity supplied by a trusted middle tier Foundry hosted session isolation The VM-isolated sandbox, represented by agent_session_id A sessio...

Amazon EVS now in scope for FedRAMP Class C - devamazonaws.blogspot.com

The Amazon Elastic VMware Service (EVS) service is now in scope for FedRAMP Class C (formerly Moderate baseline) in all United States Regions.  The   Federal Risk and Authorization Management Program (FedRAMP)  is a US government-wide program that delivers a standard approach to the security assessment, authorization, and continuous monitoring for cloud products and services. Amazon EVS lets you run the latest VMware Cloud Foundation (VCF) software directly within your Amazon Virtual Private Cloud (VPC) on EC2 bare-metal instances. You can set up a complete VCF environment in just a few hours, enabling rapid workload migration to AWS to help you eliminate aging infrastructure, reduce operational risks, and meet critical timelines for exiting your data center. To learn more, visit the FedRAMP  AWS services in scope page . To learn more about Amazon EVS, visit the  product detail page and user guide .  Post Updated on September...

[MS] Comparing exception behavior of magic statics, std::call_once, and std::async - devamazonaws.blogspot.com

We've been comparing magic statics, std:: call_ once , and std:: async , but one thing we haven't considered is their behavior in the event of an exception. For magic statics, if an exception occurs during initialization of the static, then the static is considered not to have been initialized. The exception propagates, and the next time the function is called, the language will try to initialize the static again. For call_ once , if an exception occurs during execution of the lambda, then the call is considered not to have occurred. The exception propagates, so the next time you call call_ once with the same once_ flag , it will try to call it. But std:: async is different. If an exception occurs during execution of the invocable, then the exception is saved, and when you ask the future or shared future for the result, the exception is rethrown. It does not try to execute the invocable again. Let's summarize this in a table.   Before After success After exc...