Amazon EKS Capabilities now supports Argo CD Notifications

The Amazon Elastic Kubernetes Service (Amazon EKS) Capability for Argo CD now supports Argo CD Notifications, providing notifications when your applications sync, fail, or change health. You define triggers and message templates in your cluster and subscribe individual Applications with an annotation, the same way you do in upstream Argo CD.
With this launch, you can deliver notifications to 16 notification services, including Slack, PagerDuty, Opsgenie, Amazon SQS, and Amazon EventBridge. The Amazon SQS and Amazon EventBridge services authenticate with your IAM Capability Role, so you can route deployment events into your own event-driven workflows without storing credentials in your cluster. For a service that requires third-party credentials such as a Slack token, you can specify an AWS Secrets Manager ARN in place of the secret and EKS will automatically use it on your behalf.
Notifications are available in all AWS Regions where the EKS Capability for Argo CD is available, at no additional charge. Standard charges apply for resources related to the services your notifications use, for example Amazon SQS or Amazon EventBridge. To learn more, visit Amazon EKS and refer to the Amazon EKS User Guide.
Quelle: aws.amazon.com

AWS Transform for mainframe improves the reimagine modernization workflow

AWS Transform for mainframe now discovers business functions with field-level precision and generates a new requirements coverage report in the assess and reimagine workflow. Previously, business functions that used the same table or file were grouped together, and you had to build your own traceability reporting from AWS Transform artifacts. With this launch, you can start modernizing z/OS COBOL and PL/I workloads from a more accurate catalog of business functions and verify requirements coverage before you build.
Business functions are now grouped only when they affect the same data fields. They also include screens and queues and carry clearer names and descriptions. The new requirements coverage report shows how every part of your application is accounted for in the generated requirements. Every line of source code is classified by how it was handled, every business rule links to the exact lines it came from, and every requirement is backed by the business rules that support it. You can review coverage from the full portfolio down to a single line before moving into forward engineering in Kiro and other IDEs.
These capabilities are available in all AWS Regions where AWS Transform for mainframe is available. For more information, see the AWS Region table. To learn more, visit AWS Transform for mainframe or see the AWS Transform for mainframe documentation.
Quelle: aws.amazon.com

The Platform Behind the Next AI Breakthrough

This article has been written and paid for by Microsoft. The content is not WIRED editorial content. The content does not necessarily reflect the views of WIRED, its affiliates, or owner, and does not reflect any endorsement direct or indirect of Microsoft, its affiliates, or other clients.

The next frontier of AI is coming into focus as agents take on longer, more strategic work. They can write and validate code, coordinate across systems, rebalance inventory as conditions change, manage production operations, or carry a migration from plan to completion. AI is no longer supporting one step; it is executing and reshaping the process itself.

New models help drive this change by expanding what AI can reason about, create, and accomplish. But the combination of advances in models and infrastructure is key to moving agents from isolated tasks to sustained, high-impact work. Realizing that potential requires silicon, compute, storage, and networking to work together so workloads run faster and more reliably at scale.

Agents Are a Different Kind of Workload

Cloud infrastructure has evolved before to support new kinds of applications. Even the most advanced cloud-native applications often followed predictable request-and-response paths. To deliver this at scale, cloud-native architectures turned to containers, distributed services, and dynamic scaling, to make the platform more automated and flexible. Agentic applications build on that foundation but introduce another shift: long-running work whose path and resource needs are dynamic and often unpredictable.

An agent may work for hours or days, moving between reasoning, data retrieval, tool use, and code execution while preserving progress between steps. Its needs may shift throughout the task. It might require a burst of computing power for one step, fast access to large amounts of data for another, and then pause while another tool or another agent finishes its work. Supporting this ebb and flow requires the platform to evolve again—this time around how agents operate.

Infrastructure Must Work as One System

Every layer of infrastructure is evolving for AI. Compute must respond to the changing demand of agentic workloads. Storage must preserve progress across long-running work. And networking must move data quickly among models, tools, and business systems. But improving each layer independently is no longer enough.

Agent performance depends on how well those layers are evolving and how well they all work together. More computing power will not help if the platform cannot move data quickly or maintain progress between steps. Silicon, compute, storage, and networking need to be co-designed and continuously optimized as one system.

This integrated approach also changes infrastructure operations. Teams need a complete view of performance, capacity, and cost so they can find bottlenecks and improve the full workload instead of tuning one component at a time. That system-wide view helps turn infrastructure improvements into faster, more reliable, cost-effective workloads.

Different Workloads, One Operational Approach

That consistent operational view becomes even more important as teams choose different technologies for different workloads. A customer-facing agent may prioritize low latency, while a complex workflow may need deeper reasoning. Teams need the freedom to choose the right model, run time, silicon, and environment for each workload while balancing performance and cost.

But more choice can create operational complexity because each combination may require a different approach to deployment, monitoring, and optimization. An integrated platform preserves flexibility while giving teams a consistent way to operate across models and infrastructure. Teams can choose what works best without managing every combination differently.

Levi Strauss & Co. And the Value of an Integrated Platform

Levi Strauss & Co. began its path to AI transformation by preparing existing business systems for the future. The company moved its data centers to Microsoft Azure, consolidated ERP platforms, modernized applications, and unified its data in a governed, real-time layer. But that was only the beginning.

Levi Strauss & Co. is now building a unified “super agent” to coordinate more than 1,000 domain-specific agents. Its platform must support both the critical processes that run the business today and a new class of intelligent workloads that coordinates work across functions. The lesson is clear: A durable platform must be built for current applications and whatever AI makes possible next.

Three practical tests for an agentic platform

Technical leaders can begin with three questions to assess readiness for an agentic platform.

First, do I have the high-performance compute, storage, and networking that models and agents need—or am I trying to run tomorrow’s applications on yesterday’s platform?

Second, can I choose the right model, run time, silicon, and location for each agentic workload while balancing performance, cost, complexity, and risk?

Third, can I use agents to operate the platform by moving workloads into production faster, resolving incidents before disruption, and continuously improving performance, reliability, and AI economics?

Building for the next decade

The next decade of AI will not be defined by a single breakthrough. Models will become even more capable, agents will take on work we have not yet imagined, and infrastructure demands will shift with them. Organizations need a durable platform that can embrace each new wave of innovation without being rebuilt whenever the frontier moves.

Azure is the platform foundation for that future. Microsoft has spent years bringing some of the world’s most advanced and demanding AI solutions online at massive scale. The lessons from that work continually shape Azure silicon, compute, storage, networking, and operations—and make those capabilities available to customers.

This is the opportunity of Frontier Transformation: continually turning advances across the AI stack into new ways to operate, compete, and grow.

Learn more at azure.com.
The post The Platform Behind the Next AI Breakthrough appeared first on Microsoft Azure Blog.
Quelle: Azure

Haiku 5.5 now available on Kiro in AWS GovCloud (US)

A new Anthropic model is now available in the Kiro IDE and CLI for the AWS GovCloud (US) Regions. With Haiku 5.5, all three Claude 5.5 models are now available in Kiro in AWS GovCloud (US).
Claude Haiku 5.5 is the fastest model in the Claude 5.5 family. It’s a clear step up from Claude Haiku 4.5, built for work that runs in large volumes and needs quick responses. Developers can use it to summarize and compact long context, classify and route requests, process text in bulk, and make small, targeted edits across many files. It also works well as a review subagent that runs in parallel, while Opus 5.5 and Sonnet 5.5 take on harder planning and coding work. Haiku 5.5 uses adaptive thinking across five effort levels from low to max, with medium as the default. It’s available with a 1M context window and a 0.06x credit multiplier. Requests over 100K tokens are billed at a 0.3x multiplier.
Ensure your IDE or CLI is updated to the latest version, then restart it to access the new model from the model selector. For more details, visit the GovCloud documentation, the monitoring and tracking guide, or contact your AWS account team. To learn more about Kiro, visit the Kiro product page.
Quelle: aws.amazon.com

Amazon RDS for Oracle now supports M8i and R8i instances in additional AWS Regions

Amazon Relational Database Service (Amazon RDS) for Oracle now supports M8i and R8i instances in additional AWS Regions. Both M8i and R8i instances are now available in Asia Pacific (New Zealand) and Canada West (Calgary), and R8i instances are now available in Europe (Milan, Stockholm, and Zurich) and Israel (Tel Aviv).
These instances are powered by custom Intel Xeon 6 processors, available only on AWS, delivering the highest performance and fastest memory bandwidth among comparable Intel processors in the cloud. The M8i and R8i instances offer up to 15% better price-performance, and 2.5x more memory bandwidth compared to previous generation Intel-based instances.
M8i and R8i instances are available for Amazon RDS for Oracle in Bring Your Own License model for Oracle Database Enterprise Edition (EE) and Oracle Database Standard Edition 2 (SE2). For EE, instances are available in sizes from large to 48xlarge, as well as bare metal sizes metal-48xl and metal-96xl. For SE2, instances are available in sizes from large to 4xlarge and bare metal sizes metal-48xl and metal-96xl. Refer to Amazon RDS for Oracle Pricing for available instance configurations, pricing, and region availability.
Quelle: aws.amazon.com