News For Dev-ops

Starting today, you can enable Amazon CloudWatch metric (ResolverEndpointCapacityStatus) to monitor the status of the query capacity for Elastic Network Interfaces (ENIs) associated with your Route 53 Resolver endpoint in Amazon Virtual Private Cloud (VPC). The new metric enables you to quickly view whether the Resolver endpoint is at the risk of meeting the service limit for query capacity, and take remediation steps like instantiating additional ENIs to meet the capacity needs. Before today, you could enable CloudWatch to monitor the number of DNS queries that were forwarded by Route 53 Resolver endpoints, over a default five-minute interval, and make further estimations on when your endpoints will meet the query limits. With this launch, you can now enable the new metric to get direct alerts on the current status of your Resolver endpoint capacity, without requiring you to make additional estimations for calculating capacity of each endpoint. The status is reported for each Resolve...

We are open sourcing the GitHub Copilot Chat extension. It’s the first milestone in making VS Code an open source AI editor. Read the full article Post Updated on June 30, 2025 at 01:00AM Thanks for reading from devamazonaws.blogspot.com

TL;DR Key dev updates: Agent Service hits GA with Model Context Protocol (MCP) support—integrate any backend with standardized JSON-RPC calls, no more custom OpenAPI specs. New models include o3-pro for enterprise reasoning, Sora for video generation, and DeepSeek-R1 for open-source reasoning. Platform changes: New unified Azure AI Foundry resource type consolidates management, VS Code extension gains full agent CRUD + YAML IntelliSense, and trace debugging gives you complete visibility into agent execution flows. APIs to know: Voice Live API (beta) for real-time speech interactions, enhanced Responses API with MCP tool calling, and reinforcement fine-tuning for o4-mini. Plus Foundry projects enable self-service dev environments within IT governance guardrails. Building on Azure's second consecutive year as a Gartner Leader in data science and ML platforms, these updates pair technical excellence with proven organizational frameworks that help development teams scale from pro...

Welcome to the latest roundup of key updates across the Azure Cosmos DB Java ecosystem ! The largest external customers of Azure Cosmos DB API for NoSQL, running some of the biggest and most mission critical workloads in Azure, are primarily Java users! From powerful new AI integrations to improvements in the Java SDK, Spring Data, Spark, and Kafka connectors, the past year has been transformative for developers building cloud-native and AI-powered applications. It's never been easier or more powerful to build modern Java applications on Azure Cosmos DB ! Stay tuned for more updates in the future. Happy coding! 🤖 AI Integrations In the past 12 months, Azure Cosmos DB has rolled out native support for AI development in Java , including integrations with Spring AI and LangChain4j , two leading frameworks for building AI applications. Spring AI Blog: Building multi-agent AI apps in Java with Spring AI and Cosmos DB Sample: Multi-agent orchestration in Java using Azure Cosmo...

Today, Amazon Braket introduced experimental support for dynamic circuits on IQM's Garnet quantum processing unit (QPU). This capability enables mid-circuit measurements (MCM) and feed-forward operations, allowing quantum researchers and developers to implement more advanced quantum algorithms. Dynamic circuits are a key building block for quantum error mitigation and correction. They can improve resource efficiency via qubit reuse, as well as enable experimentation with algorithms and protocols that require conditional logic. With dynamic circuits, customers can now perform active qubit reset to reuse qubits within a single circuit execution and apply conditional operations based on measurement outcomes. These techniques can reduce circuit depth requirements unlocking new capabilities on Amazon Braket. To use dynamic circuits, customers can submit verbatim programs that include mid-circuit measurement and conditional rotation instructions. These programs can be written using u...

AWS is expanding service reference information to include annotations for service actions, starting with action properties. Action properties provide context to indicate what an action is capable of, such as write or list capabilities, when you use it in a policy. Service reference information streamlines automation of policy management workflows, helping you retrieve available actions across AWS services from machine-readable files. Whether you are a security administrator establishing guardrails for workloads or a developer ensuring appropriate access to applications, you can now more easily identify the scope for each AWS service. You can automate the retrieval of service reference information, eliminating manual effort and ensuring your policies align with the latest service updates. You can also incorporate this service reference directly into your policy management tools and processes for a seamless integration. This feature is offered at no additional cost. To get started, ref...

We’re excited to introduce Dev Proxy v0.29, with a major architectural overhaul, control over language model prompts, and improved diagnostics. Whether you're building, debugging, or customizing your API simulations, this version gives you more power and clarity than ever before. In this version: Architectural refactoring to better align with .NET Dev Proxy MCP Server Exposed Dev Proxy language model prompts Improved logging with logger categories Certificate cleanup on uninstall (Windows) Bug fixes and improvements Architectural refactoring This release introduces a major refactor of Dev Proxy’s architecture to better align with .NET features. We’ve: Adopted .NET Dependency Injection to simplify object management Reorganized project structure for better clarity Replaced event-based plugin architecture with base methods Improved code consistency and alignment with .NET conventions This change allows us to set the foundation for a more scalable and maintainable projec...

We’re excited to share some major improvements to the Copilot experience in Visual Studio, including smarter default models, more choices, and easier ways to manage your usage. Smarter default model Copilot in Visual Studio now uses GPT-4.1 as the default model (previously 4o). In our testing, it delivers significantly better performance—faster responses, higher quality suggestions, and greater efficiency overall. More models to choose from Want to try something else? You now have access to an ever-broader range of models: Claude Sonnet 4 Claude Opus 4 Claude Sonnet 3.5 Claude 3.7 (non-thinking and thinking) OpenAI o3 mini Gemini 2.0 Flash Gemini 2.5 Pro Model selections are now sticky, meaning your chosen model stays selected across threads for a smoother workflow. Not sure which model to use for your task? Check out this documentation to learn about each models’ strengths . Give them a try and let us know what you think!   We’ve also made it easier to enable an...

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C7g instances are available in the AWS Israel (Tel Aviv) Region. These instances are powered by AWS Graviton3 processors that provide up to 25% better compute performance compared to AWS Graviton2 processors, and built on top of the the AWS Nitro System, a collection of AWS designed innovations that deliver efficient, flexible, and secure cloud services with isolated multi-tenancy, private networking, and fast local storage. Amazon EC2 Graviton3 instances also use up to 60% less energy to reduce your cloud carbon footprint for the same performance than comparable EC2 instances. For increased scalability, these instances are available in 9 different instance sizes, including bare metal, and offer up to 30 Gbps networking bandwidth and up to 20 Gbps of bandwidth to the Amazon Elastic Block Store (EBS). To learn more, see Amazon EC2 C7g . To explore how to migrate your workloads to Graviton-based instances, see AWS Graviton Fas...

AWS Glue now supports read and write operations from AWS Glue 5.0 Apache Spark jobs on AWS Lake Formation registered tables when the job role has full table access. This capability enables Data Manipulation Language (DML) operations including CREATE, ALTER, DELETE, UPDATE, and MERGE INTO statements on Apache Hive and Iceberg tables from within the same Apache Spark application. While Lake Formation's fine-grained access control (FGAC) offers granular security controls at row, column, and cell levels, many ETL workloads simply need full table access. This new feature enables AWS Glue 5.0 Spark jobs to directly read and write data when full table access is granted, removing limitations that previously restricted certain Extract, Transform, and Load (ETL) operations. You can now leverage advanced Spark capabilities including Resilient Distributed Datasets (RDDs), custom libraries, and User Defined Functions (UDFs) with Lake Formation tables. Additionally, data teams can run complex,...

A colleague was writing a fuzz test and ran into a build error. vccorlib.lib(climain.obj) : error LNK2019: unresolved external symbol "?main@@YAHP$01E$AAV?$Array@ PE$AAVString@ Platform@@ $00@Platform@@@Z" (?main@@YAHP$01E$AAV?$Array@ PE$AAVString@ Platform@@ $00@Platform@@@Z) referenced in function "int __cdecl _main(void)" (?_main@@YAHXZ) What does this mean? My colleague was writing a fuzz test in C++, but noted that other parts of the component are written in C++/CX. I could have guessed that C++/CX was involved because the missing symbol says that it's a function named main which takes parameters that involve things named Array , String , and Platform . The signature for the main function in a C++/CX program is int main(Platform::Array<Platform::String^>^ args) so that seems to match up with the words we picked out of the decorated name. (Amusingly, C++/CX is such a black sheep that the linker's decorated name decoder can't even dec...

We're excited to announce a significant update to Semantic Kernel Python's vector store implementation. Version 1.34 brings a complete overhaul that makes working with vector data simpler, more intuitive, and more powerful. This update consolidates the API, improves developer experience, and adds new capabilities that streamline AI development workflows. What Makes This Release Special? The new vector store architecture consolidates everything under semantic_kernel.data.vector and delivers three key improvements: Simplified API : One unified field model replaces multiple complex field types Integrated Embeddings : Embedding generation happens automatically where you need it Enhanced Features : Advanced filtering, hybrid search, and streamlined operations Let's explore what makes these changes valuable. Unified Field Model - Simplified Configuration We've replaced three separate field types with one powerful VectorStoreField class that handles everything you nee...

Now generally available, Amazon CloudWatch helps you accelerate operational investigations across your AWS environment in just a fraction of the time. With a deep understanding of your AWS cloud environment and resources, CloudWatch investigations use an AI agent to look for anomalies in your environment, surface related signals, identify root-cause hypotheses, and suggest remediation steps, significantly reducing mean time to resolution (MTTR). This new CloudWatch investigations capability works alongside you throughout your operational troubleshooting journey from issue triage through remediation. You can initiate an investigation by selecting the Investigate action on any CloudWatch data widget across the AWS Management Console. You can also start investigations from more than 80 AWS consoles, configure to auto trigger from a CloudWatch alarm action, or initiate from an Amazon Q chat. The new investigation experience in CloudWatch allows teams to collaborate and add findings, view...

Today, AWS launches Intelligent Search on AWS re:Post and AWS re:Post Private — offering a more efficient and intuitive way to access AWS knowledge across multiple sources. This new capability transforms how builders find information, providing synthesized answers from various AWS resources in one place. Intelligent Search streamlines the process of finding relevant AWS information by unifying results from re:Post community discussions, AWS Official documentation, and other public AWS knowledge sources. Instead of manually searching through multiple pages, users receive contextually relevant answers directly, saving time and effort. For instance, when troubleshooting an IAM permissions error, developers can ask a question in natural language and immediately receive a comprehensive response drawing from diverse AWS resources. This feature is particularly valuable for developers, architects, and technical leaders who need quick access to accurate information for problem-solving and d...

Amazon Bedrock Guardrails announces tiers for content filters and denied topics, offering additional flexibility and ease of use towards choosing features and expanded language support depending on customer use cases. With a new Standard tier, Guardrails now detects and filters undesirable content with better contextual understanding including modifications such as typographical errors, and support for up to 60 languages. Bedrock Guardrails provides configurable safeguards to help detect and block harmful content and prompt attacks, define topics to deny and disallow specific topics, and helps redact personally identifiable information (PII) such as personal data from input prompts and model responses. Additionally, Bedrock Guardrails helps detect and block model hallucinations, and identify, correct, and explain factual claims in model responses using Automated Reasoning checks. Guardrails can be applied across any foundation model including those hosted with Amazon Bedrock, self-ho...

One very complicated part of bringing up Plug and Play was bootstrapping the entire process. After all, the number of computers that supported the Plug and Play specification started at zero, because the specification was still being written. A lot of clever tricks were used to retrofit Plug and Play onto legacy hardware.¹ The Windows 95 team worked to gather a very large range of PC brands and models, and as part of doing "Plug and Play for PCs that predate the Plug and Play specification", the team gathered information from all of those PCs to look for clues on how they could be identified. This often included searching the BIOS for copyright strings and BIOS firmware dates. One of the strings they found was " Not Copyright Fabrikam Computer ." Why would a BIOS deny that it was copyrighted? We weren't sure, but we had a theory. Back in the early 1990's, it was not uncommon for PCs to come with preinstalled software that was locked to the manufacturer....

Today, AWS End User Messaging announces support for Service Quota. This integrations provides customers with improved visibility and control over their SMS, voice, and WhatsApp service quotas, streamlining the quota management process and reducing the need for manual intervention. With Service Quotas, customers can now view and manage their End User Messaging quota limits directly through the AWS Service Quotas console. This integration enables automated limit increase approvals for eligible requests, improving response times and reducing the number of support tickets. Customers will also benefit from visibility into quota usage for all on-boarded quotas via Amazon CloudWatch usage metrics, allowing for better resource planning and management. Service Quotas for End User Messaging is available in all commercial regions and the AWS GovCloud (US) Regions. To learn more about Service Quotas and how to manage your End User Messaging quotas, visit the Service Quotas User Guide or th...

The parser for the Microsoft MIDL compiler has long suffered from the problem of the double greater-than sign. This problem plagued C++ until C++11 added a special rule:¹ [temp.names] (4): When parsing a template-argument-list , the first non-nested > is taken as the ending delimiter rather than a greater-than operator. Similarly, the first non-nested >> is treated as two consecutive but distinct > tokens, the first of which is taken as the end of the template-argument-list and completes the template-id . Microsoft's MIDL compiler predates C++11, and its parser treats two consecutive greater-than signs as a bitwise shift operator. This means that you cannot write Windows.Foundation.IAsyncOperation< Windows.Foundation.Collections.IVector<Int32 >> when you want an asynchronous operation that produces a vector of 32-bit integers. The double-greater-than is interpreted as a shift operator, and you get a weird MIDL error message because a shift oper...

In app-only access scenarios, Shifts Management Graph APIs previously required the MS-APP-ACTS-AS: userId header to indicate the user on whose behalf the application was acting. However, this conflicted with the Microsoft Graph permission model where there is no signed-in user for app-only access scenarios. To align Shifts Graph APIs with this model, the MS-APP-ACTS-AS header has now been deprecated. What Action You Need to Take If you don’t send the header today There is no impact. No changes are necessary. If you send the header today 1. Please remove the header. Example: Old: GET /teams/{teamId}/schedule/shifts MS-APP-ACTS-AS: d56f3e8a-2b0f-42b1-88b9-e2dbd12a34d2 New: GET /teams/{teamId}/schedule/shifts 2. For offerShiftRequest , openShiftsChangeRequest , swapShiftsChangeRequest , timeOffRequest , or  timeCard, you may need to switch to a new API or add an additional property in the request body. Please see the instructions below. ScheduleChangeRequest (offerShiftReques...