# Amazon — Introducing explicit prompt caching with open-weight models on Amazon Bedrock

- Company: Amazon (amazon.com)
- Announced: 2026-11-16T15:42:41+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/use-prompt-caching-with-open-weight-models-on-amazon-bedrock/
- Record: https://forck.live/items/36735-introducing-explicit-prompt-caching-with-open-weight-models-on-amazon-bedrock
- Subject: Bedrock / Nova
- Open weights: yes

Amazon's guide shows developers how to use prompt caching with open-weight models on Amazon Bedrock, which now support explicit caching alongside implicit caching. Prompt caching reuses the computed state of a matching prompt prefix, so repeated context is read from cache instead of being processed again, which Amazon says helps reduce input costs and response latency. Implicit caching works automatically on a best-effort basis, while explicit caching lets developers mark the end of each reusable prefix with a cache breakpoint, up to the maximum the model supports. Cache reads are billed at a lower rate than standard input, though cache writes can be billed higher depending on the model. The post walks through a support assistant example using the Chat Completions API and applies implicit caching to an OpenCode coding agent session. Amazon says prompts and outputs aren't shared with the model provider or used to train models.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/use-prompt-caching-with-open-weight-models-on-amazon-bedrock/:

> Many generative AI applications send the same long context with every request, and prompt caching avoids processing it again each time. That context can be a system prompt, reference documents, tool definitions, or the conversation so far. Open-weight models on Amazon Bedrock can reuse it across requests, which helps reduce input costs and response latency.
> 
> Prompt caching reuses the computed state of a matching prompt prefix, so repeated context is read from cache instead of being processed again. Amazon Bedrock manages the cache for you. Depending on the model, you can use implicit caching, which works automatically, explicit caching, where you mark the reusable prefix, or both. The more context you reuse, and the more often you reuse it, the more you can save.
> 
> As with other models on Amazon Bedrock, your prompts and outputs aren’t shared with the model provider or used to train models. For more information, see Data protection in the Amazon Bedrock User Guide.
> 
> Open-weight models on Amazon Bedrock now support explicit prompt caching. In this post, we use both modes with an open-weight model through the Chat Completions API and show how to read cache usage from each response.

---

Record: https://forck.live/items/36735-introducing-explicit-prompt-caching-with-open-weight-models-on-amazon-bedrock
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
