Where should a shared system prompt be versioned?
Why A is the answer
Amazon Bedrock Prompt Management
Amazon Bedrock Prompt Management gives a shared prompt versions and controlled changes.
In detail
- Prompt Management versions shared prompts.
- Use versions for rollback.
Use case
An illustrative scenario, not a real incident.
Three teams share a system prompt in Prompt Management, so each change has a version.
See it in different ways
flowchart LR A["Application"] --> B["Model abstraction layer"] C["Configuration"] --> B B --> D["Model A"] B --> E["Model B"]
sequenceDiagram participant S as Service participant L as Abstraction layer participant C as Configuration participant M as Model S->>L: Request L->>C: Which model? C-->>L: Model ID L->>M: Call M-->>S: Response
flowchart LR S0["Edit"] --> S1["New version"] --> S2["Teams adopt it"]
Key point: Version shared prompts centrally.
Why the other options are wrong
- B. In a comment at the top of each Lambda function that uses the prompt
- Comments do not control what runs.
- C. In each Lambda function's environment variables
- Variables spread copies around.
- D. In the description field of the IAM role that each service is using
- An IAM description is not for prompts.