Skip to main content
Use AWS Bedrock to access various foundation models on AWS. Manage your access to models on the portal. See all the AWS Bedrock foundational models. Not all Bedrock models support all features. See the supported features for each model. We recommend experimenting to find the best-suited model for your use-case. Here are some general recommendations:
  • For a Mistral model with generally good performance, look at mistral.mistral-large-2402-v1:0.
  • You can play with Amazon Nova models. Use amazon.nova-pro-v1:0 for general purpose tasks.
  • For Claude models, see our Claude integration.

Authentication

For enhanced flexibility, Agno supports multiple authentication configuration mechanisms, including:
  • Pre-configured boto3 client
  • Custom boto3 sessions
  • Hardcoded environment variables (credentials stored in environment variables)

AwsBedrock class

The AwsBedrock class offers a set of parameters that enable you to interact with the Bedrock Converse API.

Examples

Using Hardcoded environment variables

Set your AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_REGION environment variables. Get your keys from here.
And then Use AwsBedrock with your Agent:

Using a pre-configured boto3 client or session

To enhance flexibility with boto3 clients, you can instantiate a custom boto3 client configured for the bedrock-runtime API or a boto3 session and pass it to the AwsBedrock class.

Passing additional parameters to the Bedrock API

By default, Agno allows you to configure the inferenceConfig parameter when using the bedrock-runtime API. To further customize your requests, you can include additional parameters - such as guardrailConfig, performanceConfig, and more - by passing them through the request_params field in the AwsBedrock class.
View more examples here.

Parameters

AwsBedrock is a subclass of the Model class and has access to the same params.