Skip to content

v2.21.0

Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 03 Jun 15:03
· 26 commits to refs/heads/main since this release
d3e4184

Summary

This release introduces a new BedrockAgentFunctionResolver to Event Handler that simplifies connecting AWS Lambda functions to Amazon Bedrock Agents. This feature eliminates the need to write boilerplate code for parsing requests and formatting responses, allowing you to focus on your agent's business logic.

⭐ A big thank you to @VatsalGoel3 and @svozza for their contributions to this release and to Instil for becoming a public customer reference!

Creating Amazon Bedrock Agents

Docs

You can now use the new BedrockAgentFunctionResolver to register tools and handle requests in your Lambda functions. The resolver will automatically parse the request, route it to the appropriate function, and return a well-formed response that includes the tool's output and any existing session attributes.

carbon

By default, errors are handled gracefully and returned to the agent with error type and message information, allowing the conversation to continue. This is useful when you want to let the LLM handle errors and reduce boilerplate error-handling code.

If you need more control over error scenarios, you can use BedrockFunctionResponse to customize the response and determine if the conversation should continue:

carbon

You can also use the BedrockFunctionResponse when you want to enrich the response with session attributes or knowledge base configurations, or when you want the agent to re-prompt the user to provide additional information.

carbon-2

Changes

🌟New features and non-breaking changes

  • feat(event-handler): add Amazon Bedrock Agents Functions Resolver (#3957) by @svozza
  • feat(commons): environment variable helpers (#3945) by @dreamorosi

📜 Documentation updates

🐛 Bug and hot fixes

  • fix(parameters): preserve original stack trace on transform failures … (#3982) by @VatsalGoel3

🔧 Maintenance

This release was made possible by the following contributors:

@VatsalGoel3, @dreamorosi, @hjgraca, and @svozza