New Workflow Submission: sfn-agentcore-bedrock-cdk#413
Open
NithinChandranR-AWS wants to merge 1 commit into
Open
New Workflow Submission: sfn-agentcore-bedrock-cdk#413NithinChandranR-AWS wants to merge 1 commit into
NithinChandranR-AWS wants to merge 1 commit into
Conversation
Step Functions workflow that orchestrates multiple Bedrock AgentCore agents in parallel via Map state, then aggregates responses using Bedrock Converse API. - CDK (TypeScript) infrastructure - Bundled Lambda for AgentCore SDK (not in runtime) - Parallel agent invocation with Map state - Response aggregation via Bedrock Converse
7 tasks
Author
|
Related issue: #414 |
Author
|
Hi 👋 Friendly nudge — this Step Functions + Bedrock AgentCore multi-agent orchestration workflow is ready for review. It's the first AgentCore pattern in this repo. Deployed and tested end-to-end. Would appreciate a review when you get a chance. Thank you! |
Author
|
Hi 👋 Friendly follow-up — this is the first AgentCore pattern in this repo. Shows Step Functions orchestrating multiple Bedrock AgentCore agents in parallel. Deployed and tested end-to-end. Would appreciate a review! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New Workflow: Step Functions with Bedrock AgentCore Multi-Agent Orchestration
Description
This workflow uses AWS Step Functions to orchestrate multiple Amazon Bedrock AgentCore agents in parallel via a Map state, then aggregates their responses into a unified summary using the Bedrock Converse API.
How it works:
Key architectural decisions:
@aws-sdk/client-bedrock-agentcoreSDK is not available in the Lambda runtime and must be bundled usingNodejsFunctionInvokeAgentRuntimereturns a streaming response, requiring a Lambda intermediary rather than direct Step Functions SDK integrationPattern Details
Files
example-workflow.json— Pattern metadatastatemachine/statemachine.asl.json— ASL definitionresources/statemachine.png— Workflow diagramlib/sfn-agentcore-bedrock-stack.ts— CDK stacksrc/invoke-agent.ts— Lambda: invokes AgentCore agent (bundled SDK)src/aggregate.mjs— Lambda: aggregates responses via Bedrock Conversesrc/trigger.mjs— Lambda: triggers the state machineREADME.md— Full documentation with deploy/test/cleanup instructionsTesting
Deployed and tested on AWS account with multiple AgentCore agents. The pattern correctly:
Checklist
example-workflow.jsonincludes all required fieldsAuthor
Nithin Chandran R — Technical Account Manager at AWS
LinkedIn
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.