How Bayer Crop Science built an agentic decision engine on Amazon Bedrock AgentCore with AWS Unified Operations

Bayer Crop Science leveraged Amazon Bedrock AgentCore and AWS Unified Operations to create an agentic decision engine that streamlines ML workflow insights for plant breeders via a multi‑agent, natural‑language interface.

How Bayer Crop Science built an agentic decision engine on Amazon Bedrock AgentCore with AWS Unified Operations

How Bayer Crop Science Built an Agentic Decision Engine on Amazon Bedrock AgentCore

Bayer Crop Science needed a way to make the massive, multi‑source data used in plant‑breeding decisions—genomics, field trials, imagery, environmental metrics, and model outputs—easily searchable and explainable for its scientists. Their existing Connected Decision Engine (CDE) could run and monitor thousands of machine‑learning workflows, but users still had to hop between APIs, dashboards, and logs to understand why a model behaved a certain way or why a workflow failed. To close that gap, Bayer created the Agentic Decision Engine (ADE), a natural‑language, multi‑agent front‑end that sits on top of CDE and answers questions without requiring an engineer.

---

Architecture Overview

ADE is organized into four logical layers:

  1. User Experience – A React web UI authenticates users via Microsoft Entra ID and forwards queries to the agent stack.
  2. Agent Orchestration – Amazon Bedrock AgentCore hosts containerized agents. Bayer runs its own LangGraph orchestration inside AgentCore, allowing explicit graph‑based control flow and checkpointing.
  3. Specialist Agents – A supervisor agent classifies each request and routes it to one of 22 domain‑specific agents (e.g., a Domain‑Expert agent for RAG‑based knowledge, an Operational agent for live CDE status, a Troubleshooting agent for log analysis, a Visualization agent for charts).
  4. Tools & Data Plane –

DynamoDB stores LangGraph checkpoints. Aurora PostgreSQL holds session logs, user feedback, and analytics. ElastiCache caches recent agent responses. S3 stores domain content, embedded with Titan Text Embeddings V2 and indexed in OpenSearch Serverless for Retrieval‑Augmented Generation. CloudWatch captures telemetry. AgentCore Gateway exposes backend APIs as Model Context Protocol (MCP) tools, keeping authentication and authorization outside the agent code via IAM‑scoped access.

When a breeder asks, “Why did my phenotyping workflow fail yesterday?” the supervisor routes the query to the Troubleshooting agent, which pulls telemetry from CloudWatch and status from the CDE API through the Gateway, diagnoses the failure, and returns a concise answer—all in under ten minutes, compared to the hour‑plus manual effort previously required.

---

Five Key Design Decisions

  1. Externalizing Orchestration State – AgentCore provides isolated sessions but not durable storage. Bayer persisted LangGraph checkpoints in DynamoDB, enabling workflow resumption after scaling events or session boundaries.
  2. Framework‑Agnostic Runtime – By using AgentCore’s language‑agnostic container model, Bayer could bring its preferred LangGraph orchestration and any LLM model without rewriting for a proprietary runtime.
  3. IAM‑Scoped Tool Access via AgentCore Gateway – All external tool calls (e.g., to CDE APIs, S3, OpenSearch) are mediated by the Gateway, which enforces IAM policies. This keeps security logic out of agent code and simplifies compliance.
  4. Model‑as‑Skill Registry – Model code and documentation are ingested into a central registry, allowing specialist agents to answer model‑specific questions using the model’s own metadata rather than generic LLM knowledge.
  5. Unified Operations Partnership – AWS assigned a Technical Account Manager and a Generative AI Domain Specialist Engineer to work alongside Bayer’s team. Their involvement in design reviews, weekly stand‑ups, and production readiness checks ensured that decisions aligned with both AWS service behavior and Bayer’s operational constraints.

---

Preparing for Production

Bayer followed a staged rollout:

  • CI/CD Pipeline – GitHub Actions built Docker images, pushed them to Amazon ECR, and deployed to AgentCore.
  • Testing Harness – Automated integration tests validated end‑to‑end request flows, including cache hits, fallback to specialist agents, and proper IAM enforcement.
  • Observability Stack – CloudWatch metrics, logs, and custom dashboards monitor latency, error rates, and token usage. Alerts trigger automated rollbacks for any agent container that exceeds defined thresholds.
  • Feedback Loop – User feedback stored in Aurora feeds a reinforcement‑learning‑style fine‑tuning pipeline, gradually improving response relevance.

---

Operating ADE After Launch

Post‑launch, the Unified Operations team continues to provide:

  • Performance Tuning – Adjusting instance sizes and scaling policies based on observed traffic patterns.
  • Security Audits – Periodic reviews of IAM roles attached to the AgentCore Gateway to ensure least‑privilege access.
  • Model Updates – Coordinating new LLM releases or domain‑specific model upgrades, with rollback plans baked into the CI/CD pipeline.
  • Knowledge Base Refresh – Re‑embedding updated S3 content and re‑indexing OpenSearch to keep RAG responses current.

The result is a self‑service, conversational interface that resolves roughly 80 % of user inquiries without human intervention, dramatically reducing time‑to‑insight for Bayer’s breeding teams.

---

Takeaways for Your Organization

  • Leverage Managed Agent Runtimes – Services like Amazon Bedrock AgentCore eliminate the operational overhead of building custom session isolation and tool‑access layers.
  • Persist Orchestration State Externally – Even with managed runtimes, durable state stores (DynamoDB, Aurora) are essential for reliable multi‑step workflows.
  • Adopt a Unified Operations Partner – Early collaboration with AWS TAMs and domain specialists can surface design pitfalls before they become production incidents.
  • Build a Skill Registry – Treat each model as a first‑class skill; this simplifies specialist‑agent logic and improves answer accuracy.
  • Instrument End‑to‑End Observability – Comprehensive telemetry across agents, gateways, and data sources is critical for rapid debugging and continuous improvement.

By following Bayer’s approach, organizations can transform complex ML pipelines into intuitive, conversational experiences that empower domain experts to act faster and more confidently.

Source

Read original source

Why we picked this

Details a multi‑agent platform built on Amazon Bedrock AgentCore, core AI infrastructure.

← Back to all articles