Taxonomy of agentic primitives in Amazon Quick

Antigüedad

Publicado: 6 nov 2026, 17:34 UTC
Recolectado: 6 nov 2026, 17:42 UTC

As we built Amazon Quick, its agents grew from answering questions to taking actions, and the same primitives kept getting rebuilt under different names. This post shares the taxonomy we converged on — triggers, agents, capabilities, and learned context — found by decomposing agentic work into four plain questions: When, What, Who, and How.

Extracto de la fuente

Over the past year, as we built Amazon Quick, our agents went from answering questions to taking actions: scheduling meetings, running research, generating reports. As the system evolved, one problem kept resurfacing: there was no shared definition of the primitives that agentic work is built from. The same few ideas kept getting rebuilt under different names: an actor that does the work, a signal that starts it, a packaged procedure, and a memory that carries lessons forward. This repetition…

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 47 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