← Back
AWS ML Blog

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

•14 min read•
#bedrock#agents#deployment
Level:Advanced
For:AI Engineers
✦TL;DR

Bayer Crop Science created the Agentic Decision Engine (ADE) using Amazon Bedrock AgentCore to add a multi‑agent natural‑language interface on top of its Connected Decision Engine (CDE). By leveraging AgentCore’s managed runtime, IAM‑scoped tool access, and framework‑agnostic support for LangGraph, ADE resolves roughly 80 percent of user queries without engineer involvement. The system integrates a React front‑end, Microsoft Entra ID identity proxy, GitHub Actions CI/CD to Amazon ECR, and AgentCore‑hosted containers, enabling repeatable, governed ML workflow execution at scale. Engineers can now query complex breeding analytics through a single conversational UI instead of navigating multiple operational stacks.

⚡ Key Takeaways

  • ADE resolves about 80 percent of user questions without an engineer in the loop.
  • Uses Amazon Bedrock AgentCore’s managed runtime with session isolation and IAM‑scoped tool access via AgentCore Gateway.
  • Architecture is framework‑agnostic, allowing Bayer to bring its own LangGraph orchestration and model choice.
  • Deployment pipeline: GitHub Actions builds container images, pushes to Amazon ECR, and deploys to the AgentCore runtime.
  • Prerequisite: Microsoft Entra ID identity proxy must be configured for user authentication before requests reach agents.
💡 Why It Matters

By offloading 80 % of support queries to a conversational agent stack built on Bedrock AgentCore, Bayer reduces engineer overhead and accelerates breeding decision cycles, demonstrating a production‑ready pattern for AI‑driven decision support in regulated, data‑intensive domains.

✅ Practical Steps

  1. Configure a Microsoft Entra ID identity proxy to authenticate users before they invoke ADE.
  2. Set up a GitHub Actions workflow that builds your agent’s Docker image, pushes it to Amazon ECR, and deploys it to the Amazon Bedrock AgentCore runtime.
  3. Implement IAM‑scoped tool access through the AgentCore Gateway to ensure agents can call downstream data sources without embedding credentials.

Want the full story? Read the original article.

Read on AWS ML Blog ↗

More like this

New in AWS Quick: More capable flows, an updated web experience, and agents that work together

AWS ML Blog•#agents

Three insights you may have missed from theCUBE’s coverage of the Dell Technologies New York Symposium

SiliconANGLE AI•#deployment

How Google Duplex evolved to also call businesses for you in Gemini

Google Research•#agents

Welcome Inkling 2 Mini, Cutting-edge Performance for your Local Setup

Hugging Face Blog•#llm

EXPLORE AI NEWS

Daily hand-picked stories on LLMs, RAG, agents and production AI — curated for engineers who ship.

BROWSE NEWS

GET THE WEEKLY DIGEST

Join engineers getting the Monday signal-over-noise AI breakdown. No spam, unsubscribe anytime.

LEARN AI ENGINEERING

Curated courses, research papers, repos and tutorials built for engineers leveling up in AI.

START LEARNING