Skip to main content

Amazon Bedrock Models

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 IDDescription
amazon.nova-micro-v1:0Text-only, lowest latency responses
amazon.nova-lite-v1:0Multimodal, low-cost with fast processing
amazon.nova-pro-v1:0Multimodal, balanced accuracy, speed, and cost
amazon.nova-premier-v1:0Multimodal, 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​

ParameterDescriptionDefault
aws_regionAWS region for Bedrock API requests.us-east-1
aws_profileAWS profile to use when loading credentials from shared config files.-
aws_access_key_idAWS access key ID. If not provided, credentials load from environment variables or IAM roles.-
aws_secret_access_keyAWS secret access key. If not provided, credentials load from environment variables or IAM roles.-
aws_session_tokenAWS session token for temporary credentials.-

Guardrails​

Bedrock Guardrails filter model inputs and outputs. See GuardrailConfiguration.

ParameterDescriptionDefault
bedrock_guardrail_identifierGuardrail ID or ARN. Example: arn:aws:bedrock:us-east-1:123456789012:guardrail/abc123.-
bedrock_guardrail_versionGuardrail version number or DRAFT.-
bedrock_traceTrace 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:

ParameterDescription
maxTokensMaximum number of tokens to generate.
temperatureSampling temperature (0.0 to 1.0). Lower is more deterministic.
topPNucleus sampling probability (0.0 to 1.0).
topKNumber of highest probability tokens to consider.
stopSequencesSequences that stop generation when encountered.

See Parameter Overrides for details on setting default values.

Examples​

Basic Configuration​

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

Cross-Region Inference​

Use cross-region inference profiles for improved availability:

models:
  - from: bedrock:us.amazon.nova-pro-v1:0
    name: nova-pro
    params:
      aws_region: us-east-1

With Guardrails​

models:
  - from: bedrock:amazon.nova-lite-v1:0
    name: nova-guarded
    params:
      aws_region: us-east-1
      bedrock_guardrail_identifier: arn:aws:bedrock:us-east-1:123456789012:guardrail/abc123
      bedrock_guardrail_version: '1'
      bedrock_trace: enabled

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:

      # Static credentials
      [default]
      aws_access_key_id = YOUR_ACCESS_KEY
      aws_secret_access_key = YOUR_SECRET_KEY

      # SSO profile
      [profile sso-profile]
      sso_start_url = https://my-sso-portal.awsapps.com/start
      sso_region = us-west-2
      sso_account_id = 123456789012
      sso_role_name = MyRole
      region = us-west-2
    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
    • 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:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["bedrock:InvokeModel", "bedrock:InvokeModelWithResponseStream"],
      "Resource": ["arn:aws:bedrock:us-east-1::foundation-model/amazon.nova-*"]
    }
  ]
}
PermissionPurpose
bedrock:InvokeModelRequired. Invoke model for text generation.
bedrock:InvokeModelWithResponseStreamRequired. Invoke model with streaming output.