Configuration bundles
A configuration bundle is a versioned, immutable snapshot of your agent’s dynamic configuration — system prompts, model IDs, tool descriptions, and any other key-value pairs your agent reads at runtime. Bundles decouple agent behavior from code, enabling you to change how your agent responds without redeploying code.
Key concepts
-
Components are keyed by the ARN of the AgentCore resource they configure (for example, a runtime ARN). Each component contains a
configurationobject with arbitrary key-value pairs. -
Versions are immutable. Every update creates a new version with a unique UUID. Versions form a chain via
parentVersionIds, similar to git commits. -
Branches organize version lineage (for example,
mainline,experiment-1). -
Bundle names must start with a letter and can contain letters, digits, and underscores (no hyphens). Pattern:
[a-zA-Z][a-zA-Z0-9_]{0,99}.
When to use configuration bundles
-
A/B testing. Each variant in an A/B test references a specific bundle version. The gateway injects the bundle reference into each request.
-
Recommendations. The Recommendations API can read the current configuration from a bundle and write the optimized configuration as a new bundle version.
-
Rollback. Because versions are immutable, you can roll back to any previous version by referencing its version ID.
-
Audit trail. The version chain provides a complete history of configuration changes.
Topics
