News For Dev-ops

Today, AWS Security Hub announces support for exporting findings to Amazon S3 in CSV or JSON (OCSF) format. Security teams that need findings outside the console for use cases such as compliance reporting and audit evidence can now export findings from every findings page in the Security Hub console, including Threats, Exposure, Vulnerabilities, Posture Management, Sensitive Data, and All Findings, without building and maintaining their own extraction pipelines. With this launch, you can start an export on demand from the findings page you are viewing and have Security Hub deliver the results to an S3 bucket in your account. You can choose CSV when you want to review or share findings in a spreadsheet or export in JSON if you need these findings in Open Cybersecurity Schema Framework (OCSF) format. Findings export is available in all AWS Regions where AWS Security Hub is available. To learn more, visit the AWS Security Hub User Guide at  https://docs.aws.amazon.com/securityhub/la...

Amazon GameLift Servers now supports CPU burstability for container fleets, giving game developers greater flexibility in how compute resources are allocated and consumed at runtime. Previously, container fleets relied on a fixed CPU value that simultaneously controlled both container packing density and imposed a hard runtime cap. This dual constraint forced developers to choose between efficient resource utilization and maintaining performance headroom for their game server workloads. Game server workloads are inherently bursty, CPU demand stays low during most of a match but spikes sharply during physics calculations, AI processing, or collision detection. With CPU burstability, developers can now pack containers based on typical CPU needs while still allowing game server processes to burst into available idle instance CPU during peak demand moments. This opt-in feature is configured per container group definition, supports high-density deployments without sacrificing peak performa...

We are excited to announce a new editing experience for Wiki pages. We are replacing the existing editor with a new editor built on Monaco Editor , the same editor technology that powers Visual Studio Code. Monaco brings many of the editing capabilities familiar to Visual Studio Code to Wiki pages, while preserving the functionality of the existing Wiki editor. New features The new Monaco based editor includes: ** Visual Studio Code style Markdown editing** with syntax highlighting and line numbers Native find and replace for quickly locating and updating content Improved undo and redo for formatting, pasting, attachments, and autocomplete Autocomplete support using '!' for pull requests, '@' for people, '#' for work items, as well as Wiki links and templates ** Persistent editor preferences** word wrap and synchronized scrolling If you are already familiar with Visual Studio Code, the new editor should feel familiar and provide a better exp...

On April 1, 2027, SharePoint Online and OneDrive will begin removing pre-authenticated URLs, the self-issued tokens SharePoint embeds directly in a URL, commonly seen as the tempauth query parameter. After that date, URLs returned by the affected Microsoft Graph file APIs will require Entra authentication. If your application downloads, uploads, previews, converts, or monitors file operations through Microsoft Graph, now is the time to plan your move to Microsoft Entra ID access tokens. Key message URLs returned by the affected Microsoft Graph file APIs will stop carrying embedded authorization. Any URL that previously worked without an Authorization header must now be called with a valid Microsoft Entra ID access token. Where a Microsoft Graph alternative exists, a new tenant setting lets administrators opt your app in to receiving Microsoft Graph URLs you redeem with the Graph token you already hold. Everywhere else, acquire a SharePoint Online token and present it. Background...

A database driver sits on the critical path of many applications. When a frequently executed path performs unnecessary work, even a small amount of overhead can compound across millions of operations. Over the past several releases, we have systematically profiled frequently executed paths across the Microsoft JDBC Driver for SQL Server, identifying opportunities to improve efficiency without changing application behavior. What began with ResultSet processing expanded into bulk copy operations, parameter metadata, Always Encrypted, and authentication. The work followed a consistent principle: measure where the cost is, understand why it exists, and remove unnecessary work while preserving correctness and compatibility. We focused on several critical execution paths: ResultSet: More efficient value processing and reduced decoding overhead Memory: Reduced allocation pressure across frequently executed paths Bulk copy: More efficient execution and broader use of the bu...

Gunnar Dalsnes wondered how ud0 and ud1 could have parameters if they were undefined ? "Does it mean they were not completely undefined, just undocumented and not completely implemented?" The opcodes ud0 and ud1 have no definition, but that's not the same as being architecturally an "undefined instruction". They live in a purgatory where they were not assigned a meaning, but were also not officially declared to be meaningless. Originally, these byte sequences went through the instruction decoder and happened to slip through a few cracks before somebody finally noticed, "Wait a second, I don't know how to execute this." You can see this when you look at the instructions that are encoded as 00001111 11111xxx , as of the Pentium III. Bits Bytes Opcode Operand 1 Operand 2 Meaning 00001111 11111000 0F F8 PSUBB mm mm/m64 Subtract packed bytes 00001111 11111001 0F F9 PSUBW mm mm/m64 Subtract packed words 00001111 111110...