Pegasus v1.2 - 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.

Pegasus v1.2

TwelveLabs logo. TwelveLabs — Pegasus v1.2

Model Details

Pegasus v1.2 is TwelveLabs' video-to-text generation model that produces detailed descriptions, summaries, and answers about video content. For more information about model development and performance, see the model/service card.

  • Model launch date: Feb 11, 2025

  • EOL no sooner than: Feb 11, 2026

  • Legacy period: at least 6 months

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

  • Model EOL date: March 22, 2027

  • End User License Agreements and Terms of Use: View

  • Model lifecycle: Legacy

  • Marketplace product ID: prod-635pcy5x5pc2a

Input Modalities Output Modalities APIs supported Endpoints supported
not-supported Audionot-supported Embeddingnot-supported Responsessupported bedrock-runtime
not-supported Imagenot-supported Imagenot-supported Chat Completionsnot-supported bedrock-mantle
not-supported Speechnot-supported Speechsupported Invoke
supported Textsupported Textnot-supported Converse
supported Videonot-supported Video
Tip

Whenever possible, we recommend using the bedrock-runtime endpoint for new applications. See Inference 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 twelvelabs.pegasus-1-2-v1:0 https://bedrock-runtime.{region}.amazonaws.com

us.twelvelabs.pegasus-1-2-v1:0

eu.twelvelabs.pegasus-1-2-v1:0

apac.twelvelabs.pegasus-1-2-v1:0

global.twelvelabs.pegasus-1-2-v1:0

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
supported not-supported not-supported not-supported

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.

Region In-Region Geo Global
us-east-1 (N. Virginia)supportedsupportedsupported
us-east-2 (Ohio)not-supportedsupportedsupported
us-west-1 (N. California)not-supportedsupportedsupported
us-west-2 (Oregon)not-supportedsupportedsupported
ca-central-1 (Canada)not-supportednot-supportedsupported
ca-west-1 (Calgary)not-supportednot-supportedsupported
eu-central-1 (Frankfurt)not-supportedsupportedsupported
eu-central-2 (Zurich)not-supportedsupportedsupported
eu-north-1 (Stockholm)not-supportedsupportedsupported
eu-south-1 (Milan)not-supportedsupportedsupported
eu-south-2 (Spain)not-supportedsupportedsupported
eu-west-1 (Ireland)not-supportedsupportedsupported
eu-west-2 (London)not-supportedsupportedsupported
eu-west-3 (Paris)not-supportedsupportedsupported
ap-east-2 (Taipei)not-supportednot-supportedsupported
ap-northeast-1 (Tokyo)not-supportednot-supportedsupported
ap-northeast-2 (Seoul)supportedsupportedsupported
ap-northeast-3 (Osaka)not-supportednot-supportedsupported
ap-south-1 (Mumbai)not-supportednot-supportedsupported
ap-south-2 (Hyderabad)not-supportednot-supportedsupported
ap-southeast-1 (Singapore)not-supportednot-supportedsupported
ap-southeast-2 (Sydney)not-supportednot-supportedsupported
ap-southeast-3 (Jakarta)not-supportednot-supportedsupported
ap-southeast-4 (Melbourne)not-supportednot-supportedsupported
ap-southeast-5 (Malaysia)not-supportednot-supportedsupported
ap-southeast-7 (Thailand)not-supportednot-supportedsupported
il-central-1 (Tel Aviv)not-supportednot-supportedsupported
me-central-1 (UAE)not-supportednot-supportedsupported
me-south-1 (Bahrain)not-supportednot-supportedsupported
af-south-1 (Cape Town)not-supportednot-supportedsupported
sa-east-1 (São Paulo)not-supportednot-supportedsupported
mx-central-1 (Mexico)not-supportednot-supportedsupported

Geo inference details

Geo: US

Geo Inference ID: us.twelvelabs.pegasus-1-2-v1:0

Source Region Destination Regions
us-east-1 (N. Virginia)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-1 (N. California), us-west-2 (Oregon)
us-east-2 (Ohio)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)
us-west-1 (N. California)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-1 (N. California), us-west-2 (Oregon)
us-west-2 (Oregon)us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon)

Geo: EU

Geo Inference ID: eu.twelvelabs.pegasus-1-2-v1:0

Source Region Destination Regions
eu-central-1 (Frankfurt)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-central-2 (Zurich)eu-central-1 (Frankfurt), eu-central-2 (Zurich), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-north-1 (Stockholm)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-south-1 (Milan)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-south-2 (Spain)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-west-1 (Ireland)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)
eu-west-2 (London)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-2 (London), eu-west-3 (Paris)
eu-west-3 (Paris)eu-central-1 (Frankfurt), eu-north-1 (Stockholm), eu-south-1 (Milan), eu-south-2 (Spain), eu-west-1 (Ireland), eu-west-3 (Paris)

Geo: APAC

Geo Inference ID: apac.twelvelabs.pegasus-1-2-v1:0

Source Region Destination Regions
ap-northeast-2 (Seoul)ap-northeast-1 (Tokyo), ap-northeast-2 (Seoul), ap-northeast-3 (Osaka), ap-south-1 (Mumbai), ap-south-2 (Hyderabad), ap-southeast-1 (Singapore), ap-southeast-2 (Sydney), ap-southeast-4 (Melbourne)

Global inference details

Global Inference ID Americas EMEA Asia Pacific
global.twelvelabs.pegasus-1-2-v1:0
  • us-east-1 (N. Virginia)

  • us-east-2 (Ohio)

  • us-west-1 (N. California)

  • us-west-2 (Oregon)

  • ca-central-1 (Canada)

  • ca-west-1 (Calgary)

  • sa-east-1 (São Paulo)

  • mx-central-1 (Mexico)

  • eu-central-1 (Frankfurt)

  • eu-central-2 (Zurich)

  • eu-north-1 (Stockholm)

  • eu-south-1 (Milan)

  • eu-south-2 (Spain)

  • eu-west-1 (Ireland)

  • eu-west-2 (London)

  • eu-west-3 (Paris)

  • il-central-1 (Tel Aviv)

  • me-central-1 (UAE)

  • me-south-1 (Bahrain)

  • af-south-1 (Cape Town)

  • ap-east-2 (Taipei)

  • ap-northeast-1 (Tokyo)

  • ap-northeast-2 (Seoul)

  • ap-northeast-3 (Osaka)

  • ap-south-1 (Mumbai)

  • ap-south-2 (Hyderabad)

  • ap-southeast-1 (Singapore)

  • ap-southeast-2 (Sydney)

  • ap-southeast-3 (Jakarta)

  • ap-southeast-4 (Melbourne)

  • ap-southeast-5 (Malaysia)

  • ap-southeast-7 (Thailand)

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='twelvelabs.pegasus-1-2-v1:0', body=json.dumps({ 'inputPrompt': 'Tell me about this video', 'mediaSource': { 's3Location': { 'uri': 's3://your-bucket/your-video.mp4', 'bucketOwner': '123456789012' } }, 'maxOutputTokens': 4096 }) ) print(json.loads(response['body'].read()))