← All speakers

Bio, Work & Ideas

Du’An Lightfoot

Conference affiliation: Amazon Web Services (AWS) · 2025

Du’An Lightfoot is a senior AI engineer at Akamai and the creator of LabEveryday, an educational platform for engineers developing practical technology skills. His career spans enterprise networking, cloud infrastructure, autonomous agents, and the operational demands of running language models on dedicated hardware.

An Air Force veteran, Lightfoot worked in technical support, systems administration, and enterprise networking, including at Cerner, before joining Cisco as a DevNet content developer engineer. There, he helped infrastructure engineers adopt Python, APIs, Ansible, and network automation through technical writing and developer education.

He created LabEveryday while pursuing networking certifications, motivated partly by the scarcity of Black educators in the technical communities where he was learning. He later joined AWS as a senior cloud networking developer advocate, expanding into generative AI and agent development.

At AI Engineer World’s Fair 2025, Lightfoot co-led a workshop on browser agents and the Model Context Protocol with Banjo Obayomi. His contribution emphasized agents that plan, use tools, evaluate outcomes, and adjust their behavior, while reserving deterministic automation for simpler tasks.

Lightfoot subsequently moved from AWS to Akamai, where he built reusable Kubernetes workshop infrastructure for GPU-backed inference. His work now focuses on self-hosted AI inference, vLLM, dedicated accelerators, workload isolation, and production reliability.

  • Inference needs infrastructure-aware engineering. Lightfoot treats GPU memory bandwidth, key-value cache pressure, batching, tail latency, admission control, and external queues as first-class production concerns. An available endpoint can still fail users when concurrent demand overwhelms the system, as he details in his analysis of inference failure modes.
  • Dedicated GPU inference gives agent builders operational control. His vLLM-on-LKE deployment project creates an OpenAI-compatible model endpoint on Linode Kubernetes Engine, with monitoring, load testing, security guidance, and agent integration. The approach addresses privacy, compliance, latency, rate limits, and unpredictable token costs.
  • Network MCP makes infrastructure actionable for agents. His open-source network diagnostics server equips agents to investigate connectivity, routing, DNS, and packet behavior, applying his networking background to tool-enabled AI systems.
  • Agent evaluation and human oversight determine whether automation is dependable. Lightfoot stresses continuous evaluation, guardrails, verification, and human intervention when browser sessions, authentication, CAPTCHA challenges, or ambiguous tasks exceed an agent’s practical capabilities.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Follow a browser agent from its planning loop to coffee-maker searches, MCP integration, and a multi-agent migration workflow, including the live failures that reveal where control and verification belong.

  • When does a task need an agent?
    1:39 ↗
  • From a ready-made assistant to a programmable agent
    4:40 ↗
  • Add browser actions, then prepare the workshop
    7:19 ↗
  • Search for a coffee maker without writing selectors
    16:16 ↗
  • Parallel searches expose a different set of limits
    23:36 ↗
  • Let an MCP client choose the browser operations
    31:57 ↗
  • A Wi-Fi query gets stuck at reCAPTCHA
    34:24 ↗
  • Combine documentation and diagram tools in Strands
    41:53 ↗
  • Choose managed agents or code-first composition
    47:18 ↗
  • Specify dependencies without prescribing every tool call
    48:49 ↗
  • More ambitious browser tasks need more precise control
    55:15 ↗
  • Try draw.io, then move the same server to Cursor
    1:03:08 ↗
  • Separate the planner, browser process, and cloud model
    1:11:05 ↗
  • Make browser actions and their results inspectable
    1:14:09 ↗
  • Use specialist agents as tools for a migration plan
    1:20:19 ↗
  • Architecture trouble, pricing lookups, and a deck still in progress
    1:23:34 ↗

References