Skip to main content
AWS Bedrock serves foundation models from Anthropic, Meta, Mistral, Amazon and others through a single AWS API, billed on your AWS account. In SentiVue Talk it drives the language model.

​
What you need

Both come from one IAM access key pair.

​
Getting your credentials

  1. Sign in to the AWS console and open Security credentials for the IAM user you want SentiVue Talk to use.
  2. In the Access keys section, choose Create access key. A user can hold two keys at most — delete one first if the button is greyed out.
  3. Choose Other as the use case, then Next.
  4. Choose Create access key.
  5. Copy the access key ID and the secret access key, or download the .csv. This is the only time the secret is shown — if you lose it, delete the key and create another.
The user needs bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream on the models you intend to call.
Bedrock enables third-party models on first use by subscribing your account through AWS Marketplace. That subscription needs aws-marketplace:Subscribe, aws-marketplace:Unsubscribe and aws-marketplace:ViewSubscriptions, and a valid payment method on the account. Without them the first call fails with an access-denied error. Once a model is enabled on the account, the Marketplace permissions are no longer needed to invoke it.
Anthropic models additionally require a one-time use-case form, submitted once per account or AWS organization. Select an Anthropic model in the Bedrock console and complete the form before your first call — access is granted as soon as it is submitted.

​
Adding the connection

  1. Go to Connections and choose AWS Bedrock.
  2. Paste the access key ID and the secret access key.
  3. Save.
Saving checks only that both fields are filled in. A key pair that is wrong, disabled, or missing Bedrock permissions saves without complaint and first shows up on a live call, so place a test call to confirm the connection works.

​
What you can select afterwards

Choose your models on Model Configurations. Language model — Bedrock uses IDs like anthropic.claude-haiku-4-5-20251001-v1:0. Copy the ID exactly; a shortened value is not resolved. Browse them on AWS’s models at a glance page. Which models a region serves differs — check regional availability before settling on one.

​
Completing the pipeline

Bedrock has no voice and no transcription. You also need: Each is a separate connection.

​
Troubleshooting

The usual cause is the model not yet being enabled on your AWS account. Bedrock subscribes you through AWS Marketplace on the first invocation, and that fails silently if the IAM user lacks the aws-marketplace permissions or the account has no valid payment method. Check both, then retry — a subscription can take a couple of minutes to complete, during which calls keep failing. For Anthropic models, confirm the one-time use-case form has been submitted for the account.
Copy the model ID exactly as AWS lists it, including the provider prefix and the trailing version, as in anthropic.claude-haiku-4-5-20251001-v1:0. If the ID is correct, the model may not be served in the region your account is calling — availability differs by region. Check the model on AWS’s models at a glance page.
Confirm the secret access key was copied whole — it is shown once at creation, and a truncated or re-typed value fails authentication. Check the key is still Active in IAM and has not been deleted or rotated. A key that authenticates but is denied on Bedrock is missing bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream rather than being invalid.
Check whether the access key was deactivated, deleted or rotated in IAM, or the IAM user’s permissions narrowed. Also check the AWS account for a billing hold — an account with no valid payment method loses Bedrock access without any change on your side.