← All speakers

Elizabeth Fuentes Leone

Conference affiliation: Developer Advocate · Amazon Web Services (AWS) · 2026

Elizabeth Fuentes Leone builds teaching projects that show how machine-learning applications work beyond the model: connecting recommendations to user feedback, checking whether an agent’s action succeeded, and preventing stored instructions from influencing later decisions. An AI engineer and developer advocate, she represented AWS at AI Engineer World’s Fair 2026. Her open-source examples make these application decisions available for developers to inspect and test.

On this page

From machine-learning tutorials to complete applications

Elizabeth’s 2021 SageMaker tutorial walked Spanish-speaking developers through preparing data, training and deploying an XGBoost model for a bank-marketing prediction task, and evaluating its results. It also covered deleting resources to stop further cloud charges.

A personal interest supplied a more expansive application example. After losing touch with the anime recommendations she once exchanged with university friends, Elizabeth built a personalized anime-recommendation learning project. Beginning in January 2023, the series connected Amazon Personalize to a REST API, a web interface, authentication and measurement of user engagement. Readers could follow the path from historical ratings to recommendations, then feed new interactions back into the system. The project explained both how to produce recommendations and how to learn from people using them.

Her Strands Agent Samples extend that approach to agents. Introductory notebooks cover agents and tool integration; a multimodal travel assistant brings together images, documents, video and memory. Further examples cover agent communication, tracing, evaluation and cloud deployment. Elizabeth’s contribution is the collection of applications and learning materials built with Strands Agents.

Checking what an agent actually did

Elizabeth’s agent projects examine the gap between a plausible response and a completed operation. Her work on agent failures and session on agent hallucinations develop several complementary approaches:

  • Validation before confirmation. An executor-validator-critic workflow separates attempting an operation from checking its outcome and approving the result. A failed booking should remain a failed booking rather than becoming a confident confirmation in the agent’s response.
  • Selecting tools and retrieving complete answers. Semantic tool filtering uses embeddings and top-k retrieval to expose relevant tools for a request while retaining conversation history. For questions requiring counts, aggregations or multi-hop reasoning, her GraphRAG examples use Neo4j and Cypher to query relationships across a dataset; a few retrieved text passages may leave those questions only partly answered.
  • Enforcing rules while allowing recovery. Lifecycle hooks check requirements such as capacity limits and verified payment before tools execute. Steering can redirect a recoverable violation—for example, splitting a large group across rooms—while preserving a hard stop when payment has not been verified. The examples distinguish a constraint that requires a different plan from one that forbids proceeding.

In Agent Speedrun, Elizabeth and Sandhya Subramani jointly demonstrate how these concerns carry into deployment. Their customer-service agent looks up accounts, checks orders and handles refunds. A hook limits tool invocations, exposing a useful distinction: blocking another tool call does not necessarily end the agent’s turn. They also demonstrate contextual instructions and steering, then deploy the application to Amazon Bedrock AgentCore with observability for sessions, traces and token use.

What agents retain and reuse

Elizabeth’s writing also examines decisions that persist beyond a single tool call: which memories an agent saves and when a previous computation remains applicable.

  • Screening persistent memory. Her memory-poisoning experiments use a travel assistant to show how a planted instruction can influence later booking decisions. She explores screening memories as they are written, combining rules with a model-based classifier. A related action-control example checks email destinations against an allowlist before a tool executes. These checks address separate failure points: retaining a malicious instruction and carrying out an unauthorized action.
  • Reusing work without overlooking changed requirements. Her caching designs distinguish reducing input-token costs from avoiding repeated computation by reusing answers, tool results or planning trajectories. Semantic similarity alone cannot establish that a cached result applies: two flight questions can look nearly identical while specifying different dates. Her implementation comparison therefore checks dates and numbers separately, checks expiry when reading entries, and explains why personal or tenant-specific responses require additional protections in shared caches.

Read the topics behind these talks

3 conference talks

Loading more talks and highlights…

References