Amazon Bedrock Adds Explicit Prompt Caching for Open-Weight Models
AWS announced that open-weight models on Amazon Bedrock now support explicit prompt caching, alongside model-dependent implicit caching. Prompt caching reuses computed state for matching prompt prefixes, while explicit mode lets developers mark reusable content with cache breakpoints through the Chat Completions API. AWS says this can reduce input costs and response latency, but the reported benefits remain vendor claims.
Explicit caching gives developers more control over reusing long, stable context for agent loops, shared instructions, and reference documents 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. We then apply implicit caching to an OpenCode coding agent session on the same API and close with best practices.