Exam-style
Thirty microservices each embed a copy of the same three Bedrock system prompts as string literals, so a single wording fix means thirty pull requests. The team wants one place to store prompts, version them, and have each service reference a specific version. What fits?
Reveal the answer
A. Bedrock Prompt Management, with each service referencing a published prompt version by identifier
Bedrock Prompt Management stores prompts as managed, versioned resources, so a wording change becomes a new published version and each service moves to it when ready rather than in thirty synchronised deployments. Parameter Store and a shared Lambda layer can both hold the text, but neither gives prompt-shaped versioning, variables, or testing, and both leave the team building the registry themselves. Knowledge Bases retrieve grounding documents for RAG, not prompt templates, and Agents orchestrate tool calls rather than acting as a prompt store.
Q. Thirty services share prompts and you need versioning and reuse. What on Bedrock?
A. Bedrock Prompt Management stores, versions, and shares prompts as managed resources, so a service references a version instead of copy-pasting prompt text. Prompt cachingReusing the model’s already-processed prefix (system instructions, fixed context) across calls so you don’t pay to re-read it every time. can cut cost and latency on repeated context.
Why? Treat prompts as versioned assets, not inline strings scattered across services.