AWS releases model-agnostic PII detector using Bedrock LLMs
AWS published a configurable, model-agnostic PII detector that turns any large language model on Amazon Bedrock into a PII detector. Detection entities are defined in a prompt rather than code, so one detector adapts to new entity types without retraining. AWS says it outperforms an off-the-shelf tool across five public corpora and nine LLM-based detectors.
Sources and evidence
Summary last validated Sep 10, 2026
Reader actions
Report an issue
Use this for an incorrect summary, wrong source, duplicate story, or wrong category. Submissions are private and do not change the story automatically.
Related coverage
- open source
NVIDIA Details Five-Step Workflow for SimReady Robotics Assets
NVIDIA published a five-step workflow for converting CAD assets into SimReady robotics simulation assets using Omniverse libraries, SimReady Foundation specifications, and agentic NVIDIA skills. The process covers configuring and validating materials, collision geometry, joints, and physics properties beyond simple OpenUSD geometry conversion, preparing assets before robot behavior testing.
- agents
BlockRun and Incarna use Amazon Bedrock AgentCore payments for per-inference agent billing
Amazon Bedrock AgentCore payments lets AI agents pay for services on demand with infrastructure-enforced spending limits. Incarna's agents pay BlockRun for model inference one request at a time over x402, reducing the work of adding x402 payment support from months to days, according to an AWS Machine Learning Blog post.
- infrastructure
AWS details multi-team GPU sharing on SageMaker HyperPod
AWS published a reference architecture for sharing one Amazon SageMaker HyperPod EKS cluster across multiple teams. It uses AWS IAM Identity Center for authentication, per-team SageMaker Domains and Kubernetes namespaces for isolation, HyperPod Task Governance for fairness, and namespace-level cost allocation for chargeback.
- open source
PyTorch adds Spyre as native device via torch-spyre
PyTorch's blog details how Spyre becomes a native PyTorch device. The integration connects PyTorch's existing device, allocator, stream, and compiler abstractions through torch-spyre to the Spyre runtime and firmware. PrivateUse1 is used to give Spyre a real device registration within PyTorch.
- open source
trycua/cua computer-use agent repo hits 28,733 stars on GitHub Trending
The open-source trycua/cua repository appeared on GitHub Trending at rank 10 on 2026-10-08, with 28,733 stars, 2,039 forks, and 228 stars gained that day. Written in Rust, it provides drivers, cross-OS fleets, and benchmarks for training, evaluating, and generating data for computer-use agents across macOS and Windows.