Model-agnostic PII detection with LLMs

2mes

Antigüedad

Publicado: 10 sept 2026, 16:02 UTC
Recolectado: 10 sept 2026, 16:12 UTC

A configurable, model-agnostic detector that turns any large language model on Amazon Bedrock into a PII detector. Because the entities to detect live in a prompt rather than in code, one detector adapts to new entity types without retraining, and it outperforms an off-the-shelf tool across five public corpora and nine LLM-based detectors.

Extracto de la fuente

A configurable, instruction-driven detector that runs on any large language model (LLM) managed on Amazon Bedrock, evaluated on five public PII corpora across nine LLM-based detectors, including the OpenAI PrivacyFilter. Fine-tuning a model on real-world text creates a personally identifiable information (PII) detection problem. Training corpora are full of PII: names, home addresses, email and phone numbers, national-ID and social-security numbers, bank accounts, dates of birth. A model…

Lee el artículo completo en aws.amazon.com

overfeed.news indexa y enlaza. Publicamos un extracto breve; el artículo completo sigue en AWS Machine Learning Blog.

Más de AWS Machine Learning Blog

Inicia sesión para seguir esta fuente

AWS Machine Learning Bloghace 59 minutos

Four Amazon Bedrock inference choices that affect cost

Your Amazon Bedrock inference bill can keep climbing even after you tune prompts and application logic. Four request-level choices (cache duration, service tier, reasoning effort, and maxTokens) change how many tokens the service processes and the rate applied. We show how we tested each and how to verify the effect.

AWS Machine Learning Bloghace 2 horas

Tokenomics at scale: Track and cap Amazon Bedrock spend per IAM principal with CUR 2.0 and AWS Budgets

Get per-identity Amazon Bedrock cost visibility and enforceable spend limits using only AWS-native features, with no application code for the common case. Attribute spend with IAM principal tags, report with CUR 2.0 or Cost Explorer, and enforce with AWS Budgets actions that apply a Deny policy when a threshold is crossed.

AWS Machine Learning Bloghace 3 horas

Optimizing cost per task and proving agent ROI on Amazon Bedrock

Comparing per-token prices hides the real cost of running a model on Amazon Bedrock. This post shows how to calculate the true cost per task across four hidden cost drivers, reduce it with caching, routing, and output constraints, and prove agent ROI with human baselines, holdout experiments, and a five-dimension scorecard.

AWS Machine Learning Bloghace 3 horas

Building a self-service LLM gateway with Amazon Bedrock and LiteLLM

Build a self-service LLM gateway with LiteLLM on AWS Fargate that puts Amazon Bedrock foundation models behind an OpenAI-compatible API. Developers get instant access through a single API key, while platform teams gain per-user cost controls, quota isolation, and observability.

Más de AWS Machine Learning Blog

Four Amazon Bedrock inference choices that affect cost↗

Tokenomics at scale: Track and cap Amazon Bedrock spend per IAM principal with CUR 2.0 and AWS Budgets↗

Optimizing cost per task and proving agent ROI on Amazon Bedrock↗

Building a self-service LLM gateway with Amazon Bedrock and LiteLLM↗

Four Amazon Bedrock inference choices that affect cost

Tokenomics at scale: Track and cap Amazon Bedrock spend per IAM principal with CUR 2.0 and AWS Budgets

Optimizing cost per task and proving agent ROI on Amazon Bedrock

Building a self-service LLM gateway with Amazon Bedrock and LiteLLM