feat(sfn): AWS Step Functions + Amazon Bedrock AgentCore Harness optimized integration (CDK)#3166
Conversation
…optimized integration (CDK)
bfreiberg
left a comment
bfreiberg
left a comment
There was a problem hiding this comment.
Looks great already, minor changes required
| @@ -0,0 +1,81 @@ | |||
| { | |||
| "title": "AWS Step Functions with Amazon Bedrock AgentCore Harness Optimized Integration (CDK)", | |||
| "description": "Invoke Amazon Bedrock AgentCore harness directly from AWS Step Functions using the optimized integration — zero Lambda, Converse-shaped responses, aggregated token metrics, and CloudWatch reasoning traces.", | |||
There was a problem hiding this comment.
Description needs to be 175 characters or less
There was a problem hiding this comment.
Done, trimmed to 158 characters.
| ``` | ||
|
|
||
| ---- | ||
| Copyright 2024 Amazon.com, Inc. or its affiliates. All Rights Reserved. |
There was a problem hiding this comment.
| Copyright 2024 Amazon.com, Inc. or its affiliates. All Rights Reserved. | |
| Copyright 2026 Amazon.com, Inc. or its affiliates. All Rights Reserved. |
There was a problem hiding this comment.
Fixed, updated to 2026.
- Shorten description to 158 chars (was 207, limit 175) - Update copyright year to 2026
| @@ -0,0 +1,112 @@ | |||
| # AWS Step Functions with Amazon Bedrock AgentCore Harness Optimized Integration (CDK) | |||
|
|
|||
| This pattern invokes an Amazon Bedrock AgentCore harness directly from AWS Step Functions using the optimized integration — no AWS Lambda function required. The harness handles model inference, tool use, and multi-turn conversations, returning a Converse-shaped response with aggregated token metrics. | |||
There was a problem hiding this comment.
I think you didn't need a Lambda function before but the optimized integration has a higher timeout for example
There was a problem hiding this comment.
Good point -- reframed. The real differentiator is the 15-minute timeout vs 60 seconds on the SDK integration, not the Lambda-free aspect.
| | Response format | Raw API response | Converse-shaped (text only, tool use omitted) | | ||
| | Token metrics | Manual calculation | Aggregated across all turns automatically | | ||
| | CloudWatch traces | Not available | Turn-by-turn reasoning deep-links | | ||
| | Max timeout | AWS Lambda timeout (15 min) | 15 minutes (Task state limit) | |
There was a problem hiding this comment.
Double check the SDK integration, I think it has only a 60 seconds timeout
There was a problem hiding this comment.
Corrected -- updated the table to show 60 seconds for SDK integration. Thanks for catching that.
- SDK integration has 60-second API call timeout, not 15 min - Optimized integration's key advantage is 15-min timeout for complex agents - Lambda is optional for both, not required for SDK integration
bfreiberg
left a comment
bfreiberg
left a comment
There was a problem hiding this comment.
Looks good, thanks for your contribution. Your pattern will be merged soon.
3 participants
Description
First CDK pattern using the AWS Step Functions optimized integration for Amazon Bedrock AgentCore Harness. Zero AWS Lambda — returns Converse-shaped responses with aggregated token metrics and CloudWatch reasoning traces.
Architecture
User Input → AWS Step Functions → Amazon Bedrock AgentCore Harness (optimized) → Formatted Output
Services
Testing performed