Models & capabilities, read from an operations desk

Latest

Amazon Polly upgrades Generative voices, adds Hindi and Finnish

Amazon Polly's Generative text-to-speech engine has been upgraded in place. Speech is more expressive and reads numbers, currency and addresses more accurately. Fourteen voices were added, and Hindi and Finnish are now generally available. Voice names, API calls and pricing stay the same, so existing applications improve without changes.

What changes for operators — If your support line, order-status IVR or voice agent already uses a Polly generative voice, the new engine arrives on its own and costs nothing extra, so the work is checking that your own scripts still sound right. Listen to the calls where the voice reads back order numbers, addresses, totals and confirmation codes, since that is where AWS says accuracy improved. If you serve Finnish or Hindi speakers, or Korean, German or Brazilian Portuguese ones, the catalog now has generative options to test against what you use today. If your flow depends on speech marks, those are still not available on generative voices, so check that before you switch. Before deploying across Regions, confirm the voice you picked exists in the Region you run in.

Amazon Bedrock adds TwelveLabs video model Pegasus 1.5

For a 10-200 person B2B company, this matters only if you hold long video: recorded demos, support sessions, training material or webinars. The source's own examples come from media and sports, so any fit with sales or support recordings is our reading, not the vendor's claim. If you do have such a library, you can define a segment once, such as a pricing discussion or a product shown on screen, and get consistent JSON for every file. That feeds a CRM, a ticket queue or a search index without anyone scrubbing through footage. If you have no long video, there is nothing here for you to act on. Check the Region and the separate AWS Marketplace billing before you plan around it.

AWS adds Claude Haiku 5.5, cuts subagent costs 75%

For a 10-200 person company running support ticket routing, document classification or knowledge-base Q&A through Bedrock, this is a direct cost lever: the same volume of quick, repeatable tasks now runs at roughly a quarter of the previous Haiku price, and the new effort controls let you dial down cost on simple lookups while keeping more reasoning budget for harder cases. Paired with Opus 5.5 as the planner, Haiku 5.5 becomes the cheap execution layer for many parallel subagents, which is the architecture pattern most relevant to teams automating high-volume, low-judgment work like inbound triage, data extraction or bulk document review.

Claude Sonnet 5.5 lands on AWS Bedrock

For a company already running Bedrock-based coding assistants, alert triage, or document drafting, this is a straight cost-and-latency lever, not a new capability to evaluate from scratch: routing well-defined, high-volume tasks (SQL generation, first response to alerts, spreadsheet edits, routine document work) to Sonnet 5.5 while reserving Opus 5.5 for release debugging, security review, or contract redlining should lower per-task spend without touching the existing IAM, CloudTrail, or Guardrails setup. Teams with fixed monthly AI budgets for IDE coding agents or support-ticket triage get the clearest immediate win, since Sonnet 5.5 is pitched specifically at continuous or at-scale workloads with a fixed spend cap.

Anthropic's Opus 5.5 lands on AWS Bedrock with lower cost per task

For a 10-200 person B2B company running agentic coding assistants or document-heavy knowledge work on Bedrock, Opus 5.5 offers a direct lever: lower average cost per task and clearer step-by-step reporting during long-running sessions, which matters for anyone reviewing agent output before it reaches a customer or a contract. The catch is the new safety classifiers, which refuse more requests than earlier Opus versions in areas like biology and cybersecurity — teams with support or ops bots that occasionally touch security-adjacent topics (vulnerability triage, incident response drafting) should test refusal behavior before rolling this model into production, since a blocked response mid-workflow is worse than a slightly more expensive one.

Claude 5.1 Lands on Amazon Bedrock

If your support ticketing, sales-enablement, or internal copilots already call Claude through Bedrock, this is a low-friction upgrade: change the model ID in your existing integration rather than re-platforming. Before flipping the switch on a production workflow — a support triage bot, a CRM summarizer, a contract-review assistant — run the new version against a sample of real tickets or deals and compare output quality, latency and per-call cost side by side with the model you're currently paying for. Anthropic and AWS have not published independently verified benchmark deltas for this release as of writing, so treat any capability claims as unconfirmed until you've tested against your own data. Companies not yet on Bedrock gain another reason to consolidate model access through AWS if they're already paying for EC2, S3 or other AWS services, since it simplifies billing and IAM permissions compared to managing a separate Anthropic API key.