Create a configuration bundle
Create a configuration bundle to store a versioned snapshot of your agent’s dynamic configuration. The bundle is created with an initial version on the mainline branch.
Note
The CLI add config-bundle command saves the bundle definition to agentcore.json locally. To actually create it on the service, you must run agentcore deploy afterwards.
Code samples
Example
Request parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
|
|
String |
Yes |
Name for the bundle. Must match |
|
|
Map |
Yes |
Map of component identifier to component configuration. The key is typically the ARN of the AgentCore resource being configured (for example, a runtime ARN). Each value contains a |
|
|
String |
No |
Description of the bundle. Maximum 500 characters. |
|
|
String |
No |
Branch name for version tracking. Defaults to |
|
|
String |
No |
Commit message for the initial version. Maximum 500 characters. |
|
|
Object |
No |
Source that created this version. Contains |
|
|
String |
No |
Idempotency token. If you retry with the same token, the service returns the existing bundle instead of creating a new one. |
|
|
Map |
No |
Resource tags. Maximum 50 tags. |
Response
| Field | Type | Description |
|---|---|---|
|
|
String |
ARN of the created configuration bundle. |
|
|
String |
Unique identifier for the bundle. Format: |
|
|
String |
UUID of the initial version created with the bundle. |
|
|
Timestamp |
When the bundle was created. |
Errors
| Error | HTTP status | Description |
|---|---|---|
|
|
400 |
Invalid request parameters. Check field constraints and naming patterns. |
|
|
409 |
A bundle with the same name or client token already exists. |
|
|
402 |
You have reached the maximum number of configuration bundles for your account. |
|
|
403 |
Insufficient permissions. Verify IAM policies include |
|
|
429 |
Request rate exceeded. Retry with exponential backoff. |
|
|
500 |
Service-side error. Retry the request. |