News For Dev-ops

TL;DR Foundry Agent Service (GA): The next-gen agent runtime is production-ready — Responses API-based, end-to-end private networking, MCP auth expansion (including OAuth passthrough), Voice Live preview, and hosted agents in 6 new regions. GPT-5.4 + GPT-5.4 Pro (GA): Production-grade reasoning with integrated computer use, stronger instruction adherence, and dependable multi-step execution. Standard at $2.50/$15 per million tokens; Pro at $30/$180 for deep analytical workloads. GPT-5.4 Mini (GA): Cost-efficient small model for classification, extraction, and lightweight tool calls — the high-volume tier in a GPT-5.4 routing strategy. Phi-4 Reasoning Vision 15B: Multimodal reasoning meets the Phi family — visual understanding with chain-of-thought for charts, diagrams, and document layouts. Evaluations (GA) + Continuous Monitoring: Out-of-the-box and custom evaluators with continuous production monitoring piped into Azure Monitor — quality isn't a pre-ship checkbox anymo...

AWS Agent Registry, available through Amazon Bedrock AgentCore, is now in preview — a private, governed catalog and discovery layer for agents, tools, skills, MCP servers, and custom resources within the organization. It gives teams complete visibility into their AI landscape, enabling them to discover existing agents and tools instead of rebuilding capabilities that already exist. The registry can be accessed via the AgentCore Console UI, APIs (AWS CLI, AWS SDK), or as an MCP server that builders can query and invoke directly from their IDEs. Registry supports both IAM and OAuth (Custom JWT) based access. Teams can register resources manually through the console or API, or use URL-based discovery, which automatically retrieves metadata such as tool schemas and capability descriptions from a live MCP server or agent endpoint. Records go through an approval workflow where administrators can approve records before they become discoverable, and they can plug the registry into their exist...

Running two different Aspire AppHosts at the same time works fine — they each get their own ports. But what if you need to run multiple instances of the same AppHost? Maybe you've cloned your source code into two different directories, or you're using git worktrees and want to work with both at the same time. That fails with port conflicts. If you're running integration tests alongside development, or working with AI agents that spin up multiple Aspire instances from the same project, you've hit this problem too. Aspire 13.2 solves this with isolated mode —a new flag that assigns random ports and separate configuration to each run. The Problem: Port Collisions in Parallel Development By default, Aspire runs services on predictable ports. When you start an AppHost: aspire run It binds to specific ports defined in your dashboard config. If you have two instances of an Aspire project open and try to run both, the second one fails: Error: Port 17370 is already in us...

Starting today, Amazon EC2 Capacity Manager supports tag-based dimensions, enabling you to use tags from your EC2 resources to group and filter capacity metrics. EC2 Capacity Manager helps you monitor and optimize capacity usage across On-Demand Instances, Spot Instances, and Capacity Reservations. This launch also introduces Account Name as a new built-in dimension. You can activate up to five custom tag keys — such as environment, team, or cost-center — and use them alongside built-in dimensions like Region, Instance Type, and Availability Zone to group and filter capacity metrics by tag values in the console and APIs, and include tag data as additional columns in newly created S3 data exports. Capacity Manager also includes four Capacity Manager-provided tags by default: EC2 Auto Scaling group name, EKS cluster name, EKS Kubernetes node pool, and Karpenter node pool. The new Account Name dimension makes it easier to identify accounts when analyzing cross-account capacity data acros...

Learn what's new in Visual Studio Code 1.116 (Insiders) Read the full article Post Updated on April 15, 2026 at 06:00PM Thanks for reading from devamazonaws.blogspot.com

Amazon Location Service today announced new map styling capabilities, providing developers with greater control over terrain visualization, traffic display, and immersive 3D experiences. This release introduces customizable contour line density levels, a traffic congestion-only mode, 3D Terrain and Globe View features, and expands support for existing features across multiple map styles. These capabilities enable you to customize maps for diverse use cases. Choose from three contour line density levels (Low, Medium, and High) to control elevation data visualization, with Low density emphasizing major elevation changes, Medium density providing balanced detail, and High density showing double the contour lines for intricate terrain views. Display traffic strategically with the new traffic congestion-only mode, which filters out free-flowing traffic to highlight incidents and congestion. Create immersive experiences with 3D Terrain and 3D Globe View with Atmosphere, featuring realistic...