Amazon Bedrock Model Provider

To use an embedding model deployed to AWS Bedrock service, specify the model endpoint name prefixed with bedrock: in the from field and include the required parameters in the params section.

Parameters

AWS Parameters

Parameter	Description
aws_region	AWS region. Default: us-east-1.
aws_profile	Optional. AWS profile to use when loading credentials.
aws_access_key_id	Optional. AWS access key ID for authentication. If not provided, credentials will be loaded from environment variables or IAM roles
aws_secret_access_key	Optional. AWS secret access key for authentication. If not provided, credentials will be loaded from environment variables or IAM roles
aws_session_token	Optional. AWS session token for authentication
max_concurrent_invocations	Optional. The maximum number of concurrent API invocations. Defaults to 40
requests_per_min_limit	Optional. The maximum number of requests made per minute. Defaults to 1500

AWS Titan Models

These parameters are used for Amazon Titan Text embedding model

Parameter	Description
normalize	Whether or not to normalize the output embedding. Defaults to true.
dimensions	The number of dimensions the output embedding should have. The following values are accepted: 1024 (default), 512, 256.

Cohere Models

Parameter	Description
truncate	Specifies how the API handles inputs longer than the maximum token length. One of: START, END or NONE (default).
input_type	Use the Cohere embeddings model optimized for different types of inputs. One of: search_document (default), search_query, classification or clustering.

Example spicepod.yaml configuration, Cohere model

embeddings:
  - from: bedrock:cohere.embed-english-v3
    name: cohere-embeddings
    params:
      aws_region: us-east-1
      input_type: classification
      truncate: END
      aws_access_key_id: ${ secrets:AWS_ACCESS_KEY_ID }
      aws_secret_access_key: ${ secrets:AWS_SECRET_ACCESS_KEY }

Example spicepod.yaml configuration, Titan model

  - from: bedrock:amazon.titan-embed-text-v2:0
    name: titan-embeddings
    params:
      dimensions: "256"

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 the following permissions to access DynamoDB tables:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "bedrock:InvokeModel"
            ],
            "Resource": [
                "arn:aws:bedrock:us-east-1::foundation-model/amazon.titan-*"
            ]
        }
    ]
}

Permission Details

Permission	Purpose
bedrock:InvokeModel	Required. Used to invoke the embedding model.

Additional Information

Refer to the Amazon Bedrock documentation for more details on available models and configurations.