News For Dev-ops

Introduction In a recent engagement, we worked with a customer who already had a similarity search system backed by LanceDB. The foundation was solid: vector search over embedded documents powering retrieval for end user similarity searches. But their use case wasn’t purely semantic. Users frequently searched by identifier numbers and exact fields. They valued that LanceDB could support hybrid retrieval, allowing them to directly pinpoint a specific result while also retrieving semantically similar ones. Sure, the search system worked. But as we enhanced their system, the conversation naturally evolved into: If we were to design this from scratch, would we choose Keyword Search, or Hybrid Search? Or, more broadly: How should enterprises decide between these two architectures? Rather than answer based on intuition, we developed a structured evaluation framework. Over time, that framework distilled into five measurable criteria we now use to guide this decision. While this dis...

AWS IoT Core now provides two new Amazon CloudWatch Log event types that help you troubleshoot device connectivity issues and authentication errors across your Internet of Things (IoT) fleet. The new Ping log event type is emitted when devices send MQTT Keep-alive messages, and it enables you to identify connections or devices that were unable to keep the connection alive. The new Connection.AuthNError log event type records rejected connection attempts due to authentication failure, along with detailed error codes that tell you what went wrong, so you can resolve credential and certificate issues faster. To get started, configure event-level logging in your AWS IoT Core settings with your desired log level and Amazon CloudWatch log group destination, then opt into these new event types. The two new event types are available in all AWS Regions where AWS IoT Core is available. To learn more, see AWS IoT log entries in the AWS IoT Core developer guide. Post Updated on June 3,...

Amazon CloudWatch now allows you to query metrics data up to two weeks in the past using the Metrics Insights query source. CloudWatch Metrics Insights offers fast, flexible, SQL-based queries. This new capability allows you to display, aggregate, or slice and dice metrics data older than 3 hours, for enhanced visualization and investigation. Previously, when creating dashboards and alarms to monitor dynamic groups of metrics over your resources and applications, you could visualize up to 3 hours of data when using Metrics Insights SQL queries. This enhancement helps you identify trends and investigate impact for a longer period of time, even days after an event. This extended query time range helps improve the operational health of teams and ensures impacts are never missed. Querying metrics data up to two weeks old with Metrics Insights is now available in the AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. The ability to query metrics data up to 2 weeks old is autom...

Azure Content Understanding in Foundry Tools is Microsoft's comprehensive content AI service. It ingests diverse data types — documents, audio, images, and video — and extracts the most critical information to power well-grounded, reliable generative AI and agentic solutions. Azure Content Understanding brings together Azure Document Intelligence's proven traditional AI with advanced LLM-based content reasoning, enabling both structured and unstructured content extraction, as well as multimodal understanding to address your full spectrum of processing needs. Accelerating customer momentum Leading organizations are already using Content Understanding to move from unstructured content to production-scale automation. DataSnipper is bringing AI-powered document analysis directly into Excel workflows DataSnipper is embedding Content Understanding into everyday financial and audit workflows, allowing professionals to work directly with structured data derived from unstructured do...

Kubernetes version 1.36 introduced several new features and bug fixes, and AWS is excited to announce that you can now use Amazon Elastic Kubernetes Service (EKS) and Amazon EKS Distro to run Kubernetes version 1.36. Starting today, you can create new EKS clusters using version 1.36 and upgrade existing clusters to version 1.36 using the EKS console, the eksctl command line interface, or through an infrastructure-as-code tool. Kubernetes version 1.36 introduces several key improvements, promoting User Namespaces to general availability for mapping container root to an unprivileged host user so that a breakout grants no node-level privileges, alongside Mutating Admission Policies for CEL-based resource mutations in the API server without webhook infrastructure. The release also brings In-Place Pod-Level Resources Vertical Scaling allowing Pods to resize their shared CPU and memory budget without restart, and Resource Health Status reporting device health in Pod status to help identi...

A key phase in installing a package is staging the package: var packageUri = new Uri("C:\\Packages\\ContosoParts-v1.2.3.4-x64.msix"); var options = new StagePackageOptions(); var packageManager = new PackageManager(); var result = await packageManager.StagePackageByUriAsync(packageUri, options); When a package is staged for the first time, deployment performs several actions, including: Creating a new package directory (commonly referred to as the pkgdir ), for example C:\Program Files\WindowsApps\Contoso.Parts_1.2.3.4_x64__1234567890abc Extracting the contents of the .msix into the pkgdir Applying a tightly restricted access control list (ACL) to the pkgdir Creating related directories used for system bookkeeping associated with the package Applying similarly restrictive ACLs to these bookkeeping directories Deployment secures these directories with strict permissions, typically granting users Read and potentially Execute access - but notably not Write a...