Skip to content

docs: add Amazon Bedrock Runtime guide with Converse API examples#4727

Open
niceysam wants to merge 1 commit intoboto:developfrom
niceysam:feature/add-bedrock-guide
Open

docs: add Amazon Bedrock Runtime guide with Converse API examples#4727
niceysam wants to merge 1 commit intoboto:developfrom
niceysam:feature/add-bedrock-guide

Conversation

@niceysam
Copy link
Copy Markdown

@niceysam niceysam commented Mar 2, 2026

What's changed

Added a new guide for Amazon Bedrock Runtime at docs/source/guide/bedrock.rst covering practical use cases with the Converse API.

The Converse API has been the recommended interface since its GA in 2024 — it provides a unified message format across all foundation models and is simpler than the lower-level invoke_model. However, boto3 currently has no guide for Bedrock at all, leaving developers to piece things together from the API reference.

Examples included

  • Basic message with the Converse API
  • System prompt usage
  • Multi-turn conversation (passing conversation history)
  • Streaming responses with converse_stream
  • Cross-region inference using model ID prefix (e.g. us.)
  • Error handling (ThrottlingException, ModelNotReadyException)

Why Converse API over InvokeModel

The guide intentionally focuses on the Converse API rather than invoke_model because Converse works uniformly across all supported models without needing to know each model's specific request/response format. invoke_model is still mentioned briefly for awareness but not demonstrated, since most users are better served by Converse.

Fixes: no existing issue — this adds missing documentation for a GA service.

@niceysam niceysam force-pushed the feature/add-bedrock-guide branch from 207bbd8 to fb471d9 Compare March 2, 2026 01:50
Add a new guide covering common Amazon Bedrock Runtime use cases using
the Converse API, which is the recommended interface for conversational
workloads.

Examples included:
- Basic message with the Converse API
- System prompt usage
- Multi-turn conversation
- Streaming responses with converse_stream
- Cross-region inference with model ID prefix
- Error handling for ThrottlingException and ModelNotReadyException

The Converse API is preferred over the lower-level InvokeModel for most
use cases because it provides a unified message format across all
supported foundation models.
@niceysam niceysam force-pushed the feature/add-bedrock-guide branch from fb471d9 to ef05ecf Compare March 2, 2026 01:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant