Jamba 1.5 Large - Amazon Bedrock
Services or capabilities described in AWS documentation might vary by Region. To see the differences applicable to the AWS European Sovereign Cloud Region, see the AWS European Sovereign Cloud User Guide.

Jamba 1.5 Large

AI21 Labs logo with pink and black text. AI21 Labs — Jamba 1.5 Large

Model Details

Jamba 1.5 Large is AI21 Labs' hybrid SSM-Transformer model with 398B total parameters and a 256K context window, optimized for complex reasoning tasks across long documents. For more information about model development and performance, see the model/service card.

  • Model launch date: Aug 22, 2024

  • EOL no sooner than: Aug 22, 2025

  • Legacy period: at least 6 months

  • Model lifecycle policy: Model lifecycle (For Models Launched Prior to Sept 7 2026)

  • Model EOL date: November 26, 2026

  • End User License Agreements and Terms of Use: View

  • Model lifecycle: Legacy

  • Context window: 256K tokens

  • Max output tokens: 4K

  • Knowledge cutoff: Mar 2024

  • Marketplace product ID: prod-evcp4w4lurj26

Input Modalities Output Modalities
Red circle with white X icon indicating error, cancel, or close action. AudioRed circle with white X icon indicating error, cancel, or close action. Embedding
Red circle with white X icon indicating error, cancel, or close action. ImageRed circle with white X icon indicating error, cancel, or close action. Image
Red circle with white X icon indicating error, cancel, or close action. SpeechRed circle with white X icon indicating error, cancel, or close action. Speech
Green circle with white checkmark icon. TextGreen circle with white checkmark icon. Text
Red circle with white X icon indicating error, cancel, or close action. VideoRed circle with white X icon indicating error, cancel, or close action. Video

Endpoints and APIs supported

The following tables show which endpoints and APIs are supported for Jamba 1.5 Large. For more information, see APIs supported by Amazon Bedrock and Endpoints supported by Amazon Bedrock.

Endpoint support

Endpoint Supported
bedrock-runtime supported
bedrock-mantle not-supported

APIs supported on bedrock-runtime endpoint

Messages Responses Chat Completions Converse Invoke
not-supported not-supported not-supported supported supported

APIs supported on bedrock-mantle endpoint

Messages Responses Chat Completions Converse Invoke
not-supported not-supported not-supported not-supported not-supported
Tip

Whenever possible, we recommend using the bedrock-runtime endpoint for new applications. See Endpoints supported by Amazon Bedrock for details.

Capabilities and Features

Bedrock Features

Features supported using bedrock-runtime endpoint

Pricing

This model is a third-party model offered and billed through AWS Marketplace. Charges appear on your AWS bill and in AWS Cost Explorer under the model provider (not under Amazon Bedrock). For pricing, see the Amazon Bedrock Pricing page.

Programmatic Access

Use the following model IDs and endpoint URLs to access this model programmatically. For more information about the available APIs and endpoints, see APIs supported and Endpoints supported.

Endpoint Model ID In-Region endpoint URL Geo inference ID Global inference ID
bedrock-runtime ai21.jamba-1-5-large-v1:0 https://bedrock-runtime.{region}.amazonaws.com Not supported Not supported

For example, if region is us-east-1 (N. Virginia), then the bedrock-runtime endpoint URL will be "https://bedrock-runtime.us-east-1.amazonaws.com" and for bedrock-mantle will be "https://bedrock-mantle.us-east-1.api.aws/v1".

Service Tiers

Amazon Bedrock offers multiple service tiers to match your workload requirements. Standard provides pay-per-token access with no commitment (set "service_tier": "default" or omit the field). Priority delivers the fastest response times for a price premium (set "service_tier": "priority"). Flex provides lower-cost access for flexible, non-time-sensitive workloads (set "service_tier": "flex"). Reserved provides dedicated throughput with a term commitment for predictable workloads; it is set at the account level rather than per request (contact your AWS account team to enable). For more information, see service tiers.

Standard Priority Flex Reserved
Green circle with white checkmark icon. Red circle with white X icon indicating error, cancel, or close action. Red circle with white X icon indicating error, cancel, or close action. Red circle with white X icon indicating error, cancel, or close action.

Regional Availability

Regional availability at a glance

Amazon Bedrock offers three inference options: In-Region keeps requests within a single Region for strict compliance, Geo Cross-Region routes across Regions within a geography (such as US, EU, and APAC) while respecting data residency, and Global Cross-Region routes anywhere worldwide when there are no residency constraints. Refer to the Regional availability by models page for more details.

Availability differs by endpoint.

Availability using the bedrock-runtime endpoint

Region In-Region Geo Global
us-east-1 (N. Virginia)Green circle with white checkmark icon.Red circle with white X icon indicating error, cancel, or close action.Red circle with white X icon indicating error, cancel, or close action.

Quotas and Limits

Your AWS account has default quotas to maintain the performance of the service and to ensure appropriate usage of Amazon Bedrock. The default quotas assigned to an account might be updated depending on regional factors, payment history, fraudulent usage, and/or approval of a quota increase request. For more information, see Quotas for Amazon Bedrock documentation and see the limits for the model.

Sample Code

Step 1 - AWS Account: If you have an AWS account already, skip this step. If you are new to AWS, sign up for an AWS account.

Step 2 - API key: Go to the Amazon Bedrock console and generate a long-term API key.

Step 3 - Get the SDK: To use this getting started guide, you must have Python already installed. Then install the relevant software depending on the APIs you are using.

pip install boto3

Step 4 - Set environment variables: Configure your environment to use the API key for authentication.

AWS_BEARER_TOKEN_BEDROCK="<provide your Bedrock API key>"

Step 5 - Run your first inference request: Save the file as bedrock-first-request.py

Invoke API
import json import boto3 client = boto3.client('bedrock-runtime', region_name='us-east-1') response = client.invoke_model( modelId='ai21.jamba-1-5-large-v1:0', body=json.dumps({ 'messages': [{ 'role': 'user', 'content': 'Can you explain the features of Amazon Bedrock?'}], 'max_tokens': 1024 }) ) print(json.loads(response['body'].read()))
Converse API
import boto3 client = boto3.client('bedrock-runtime', region_name='us-east-1') response = client.converse( modelId='ai21.jamba-1-5-large-v1:0', messages=[ { 'role': 'user', 'content': [{'text': 'Can you explain the features of Amazon Bedrock?'}] } ] ) print(response)