---

title: 'Amazon Bedrock Models' description: 'How to use Amazon Bedrock models with Spice.' sidebar_label: 'Bedrock' sidebar_position: 9

Amazon Bedrock provides access to a range of foundation models for generative AI. Spice supports using Bedrock-hosted models by specifying the bedrock prefix in the from field and configuring the required parameters.

Supported Model IDs

The following model IDs are supported:

• amazon.nova-lite-v1:0
• amazon.nova-micro-v1:0
• amazon.nova-premier-v1:0
• amazon.nova-pro-v1:0

Refer to the Amazon Bedrock documentation for details on available models and cross-region inference profiles.

To request support for a model, file a GitHub Issue or ask us on Discord.

Configuration

from

Specify the Bedrock model ID in the from field:

Parameters

Parameter	Description	Default
aws_region	AWS region for Bedrock API requests.	-
aws_access_key_id	AWS access key ID. If not provided, credentials will be loaded from environment variables or IAM roles.	-
aws_secret_access_key	AWS secret access key. If not provided, credentials will be loaded from environment variables or IAM roles.	-
aws_session_token	Session token (e.g. AWS_SESSION_TOKEN for AWS) for temporary credentials	-
bedrock_guardrail_identifier	Identifier for the guardrail. See GuardrailConfiguration. Pattern: (([a-z0-9]+) | (arn:aws(-[^:]+)?:bedrock:[a-z0-9-]{1,20}:[0-9]{12}:guardrail/[a-z0-9]+)). Length: 0-2048.	-
bedrock_guardrail_version	Guardrail version. Pattern: (([1-9][0-9]{0,7}) | (DRAFT))	-
bedrock_trace	Trace behavior for the guardrail. Valid values: enabled, disabled, . Default: .

OpenAI-Compatible Overrides

The following OpenAI-compatible parameters are supported and passed in the request payload:

• maxTokens
• temperature
• topP
• topK
• stopSequences

See Parameter Overrides for details.

Example Configuration

Authentication

If AWS credentials are not explicitly provided in the configuration, the connector will automatically load credentials from the following sources in order.

1. Environment Variables:

   • AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
   • AWS_SESSION_TOKEN (if using temporary credentials)

2. Shared AWS Config/Credentials Files:

   • Config file: ~/.aws/config (Linux/Mac) or %UserProfile%\.aws\config (Windows)

   • Credentials file: ~/.aws/credentials (Linux/Mac) or %UserProfile%\.aws\credentials (Windows)

   • The AWS_PROFILE environment variable can be used to specify a named profile, otherwise the [default] profile is used.

   • Supports both static credentials and SSO sessions

   • Example credentials file:

   :::tip To set up SSO authentication:

   1. Run aws configure sso to configure a new SSO profile
   2. Use the profile by setting AWS_PROFILE=sso-profile
   3. Run aws sso login --profile sso-profile to start a new SSO session :::

3. AWS STS Web Identity Token Credentials:

   • Used primarily with OpenID Connect (OIDC) and OAuth

The connector will try each source in order until valid credentials are found. If no valid credentials are found, an authentication error will be returned.

:::note[IAM Permissions] Regardless of the credential source, the IAM role or user must have appropriate bedrock permissions (e.g., bedrock:InvokeModel) to access the model. If the Spicepod connects to multiple different AWS services, the permissions should cover all of them. :::

Required IAM Permissions

The IAM role or user needs the following permissions to access DynamoDB tables:

Permission Details

Permission	Purpose
bedrock:InvokeModel	Required. Used to invoke the text model.
bedrock:InvokeModelWithResponseStream	Required. Used to invoke the text model with streaming responses.

References

• Amazon Bedrock Documentation
• GuardrailConfiguration API
• SpiceAI Bedrock Embeddings
• Parameter Overrides