For the complete documentation index, see llms.txt. This page is also available as Markdown.

Amazon Bedrock

How to use Amazon Bedrock models with Spice.

Spice supports large language models hosted on Amazon Bedrock. Specify the bedrock: prefix in the from field along with the model ID.

Supported Models

Spice supports the following Amazon Nova models:

Model ID
Description

amazon.nova-micro-v1:0

Text-only, lowest latency responses

amazon.nova-lite-v1:0

Multimodal, low-cost with fast processing

amazon.nova-pro-v1:0

Multimodal, balanced accuracy, speed, and cost

amazon.nova-premier-v1:0

Multimodal, best for complex tasks

Cross-region inference profiles (e.g., us.amazon.nova-lite-v1:0) are also supported. See the Amazon Bedrock model IDs documentation for details.

To request support for additional models, file a GitHub Issue.

Configuration

from

Specify the Bedrock model ID in the from field:

models:
  - from: bedrock:us.amazon.nova-lite-v1:0
    name: novash
    params:
      aws_region: us-east-1
      aws_access_key_id: ${ secrets:AWS_ACCESS_KEY_ID }
      aws_secret_access_key: ${ secrets:AWS_SECRET_ACCESS_KEY }

Parameters

AWS Authentication

Parameter
Description
Default

aws_region

AWS region for Bedrock API requests.

us-east-1

aws_profile

AWS profile to use when loading credentials from shared config files.

-

aws_access_key_id

AWS access key ID. If not provided, credentials load from environment variables or IAM roles.

-

aws_secret_access_key

AWS secret access key. If not provided, credentials load from environment variables or IAM roles.

-

aws_session_token

AWS session token for temporary credentials.

-

Guardrails

Bedrock Guardrails filter model inputs and outputs. See GuardrailConfiguration.

Parameter
Description
Default

bedrock_guardrail_identifier

Guardrail ID or ARN. Example: arn:aws:bedrock:us-east-1:123456789012:guardrail/abc123.

-

bedrock_guardrail_version

Guardrail version number or DRAFT.

-

bedrock_trace

Trace output for guardrail evaluation. One of: disabled, enabled, enabled_full.

disabled

Model Parameters

These parameters control model behavior and are passed in the request payload:

Parameter
Description

maxTokens

Maximum number of tokens to generate.

temperature

Sampling temperature (0.0 to 1.0). Lower is more deterministic.

topP

Nucleus sampling probability (0.0 to 1.0).

topK

Number of highest probability tokens to consider.

stopSequences

Sequences that stop generation when encountered.

See Parameter Overrides for details on setting default values.

Examples

Basic Configuration

Cross-Region Inference

Use cross-region inference profiles for improved availability:

With Guardrails

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:

  3. AWS STS Web Identity Token Credentials:

    • Used primarily with OpenID Connect (OIDC) and OAuth

    • Common in Kubernetes environments using IAM roles for service accounts (IRSA)

  4. ECS Container Credentials:

    • Used when running in Amazon ECS containers

    • Automatically uses the task's IAM role

    • Retrieved from the ECS credential provider endpoint

    • Relies on the environment variable AWS_CONTAINER_CREDENTIALS_RELATIVE_URI or AWS_CONTAINER_CREDENTIALS_FULL_URI which are automatically injected by ECS.

  5. AWS EC2 Instance Metadata Service (IMDSv2):

    • Used when running on EC2 instances.

    • Automatically uses the instance's IAM role.

    • Retrieved securely using IMDSv2.

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.

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 permissions to invoke Bedrock models:

Permission
Purpose

bedrock:InvokeModel

Required. Invoke model for text generation.

bedrock:InvokeModelWithResponseStream

Required. Invoke model with streaming output.

Last updated

Was this helpful?