Description
agentcore add config-bundle succeeds and agentcore deploy -y completes without error, but the deployed config bundles are never recognized by the service. Running agentcore cb versions --bundle NutritionControl returns Error: Configuration bundle "NutritionControl" not found. Has it been deployed?, and agentcore status shows both bundles as "Local only" even after a successful deploy.
Attempting to re-add the bundles with --branch and --commit-message flags then fails with "Configuration Bundle already exists," creating a dead-end where the bundles exist locally (blocking re-creation) but were never actually provisioned remotely (blocking version queries or A/B test usage).
The root cause appears to be that agentcore deploy does not actually deploy config bundles to the service — it only deploys the runtime/memory infrastructure — leaving bundles stranded in local state with no CLI path to push them to the remote.
Steps to Reproduce
CONTROL_PROMPT=$(cat app/personalAgent/system-prompt.txt | jq -Rs .)
agentcore add config-bundle \
--name NutritionControl \
--components "$(jq -n --arg prompt "$(cat app/personalAgent/system-prompt.txt)" \
'{"{{runtime:personalAgent}}": {"configuration": {"systemPrompt": $prompt}}}')"
Added configuration bundle 'NutritionControl'
(.venv) (py313) sagemaker-user@default:~/agentcore-runtime-quickstart/personalAgent$ agentcore deploy -y
✓ Load deployment target
✓ Validate project
✓ Build CDK project
✓ Synthesize CloudFormation
✓ Check bootstrap status
✓ Check stack status
✓ Deploy to AWS
✓ Persist deployment state
✓ Deployed to 'default' (stack: AgentCore-personalAgent-default)
Outputs:
ApplicationAgentPersonalAgentRoleArnOutputD767CFF3: arn:aws:iam::227017984506:role/AgentCore-personalAgent-d-ApplicationAgentPersonalA-DpVMFPyedKB3
ApplicationMemoryNames676588DB: SharedMemory
ApplicationAgentPersonalAgentRuntimeIdOutputBEC9CA78: personalAgent_personalAgent-bpV5TVHepU
ApplicationMemorySharedMemoryArnOutputCDD403B7: arn:aws:bedrock-agentcore:us-east-1:227017984506:memory/personalAgent_SharedMemory-2a20R7622q
ApplicationAgentPersonalAgentRuntimeArnOutput79B88F18: arn:aws:bedrock-agentcore:us-east-1:227017984506:runtime/personalAgent_personalAgent-bpV5TVHepU
ApplicationMemoryIds538D889E: personalAgent_SharedMemory-2a20R7622q
ApplicationMemorySharedMemoryIdOutput00409E82: personalAgent_SharedMemory-2a20R7622q
StackNameOutput: AgentCore-personalAgent-default
Note: Transaction search enabled. It takes ~10 minutes for transaction search to be fully active and for traces from invocations to be indexed.
Next: agentcore invoke | agentcore status
Log: agentcore/.cli/logs/deploy/deploy-20260504-213520.log
(.venv) (py313) sagemaker-user@default:~/agentcore-runtime-quickstart/personalAgent$ agentcore add config-bundle \
--name NutritionTreatment \
--components "$(jq -n --arg prompt "$(cat rapp/personalAgent/system-prompt.txt)" \
'{"{{runtime:personalAgent}}": {"configuration": {"systemPrompt": $prompt}}}')"
cat: rapp/personalAgent/system-prompt.txt: No such file or directory
^C(.venv) (py313) sagemaker-user@default:~/agentcore-runtime-quickstart/personalAgent$ agentcore add config-bundle \ agentcore add config-bundle \
--name NutritionTreatment \
--components "$(jq -n --arg prompt "$(cat app/personalAgent/system-prompt.txt)" \
'{"{{runtime:personalAgent}}": {"configuration": {"systemPrompt": $prompt}}}')"
Added configuration bundle 'NutritionTreatment'
(.venv) (py313) sagemaker-user@default:~/agentcore-runtime-quickstart/personalAgent$ agentcore deploy -y
✓ Load deployment target
✓ Validate project
✓ Build CDK project
✓ Synthesize CloudFormation
✓ Check bootstrap status
✓ Check stack status
✓ Deploy to AWS
✓ Persist deployment state
✓ Deployed to 'default' (stack: AgentCore-personalAgent-default)
Outputs:
ApplicationAgentPersonalAgentRoleArnOutputD767CFF3: arn:aws:iam::227017984506:role/AgentCore-personalAgent-d-ApplicationAgentPersonalA-DpVMFPyedKB3
ApplicationMemoryNames676588DB: SharedMemory
ApplicationAgentPersonalAgentRuntimeIdOutputBEC9CA78: personalAgent_personalAgent-bpV5TVHepU
ApplicationMemorySharedMemoryArnOutputCDD403B7: arn:aws:bedrock-agentcore:us-east-1:227017984506:memory/personalAgent_SharedMemory-2a20R7622q
ApplicationAgentPersonalAgentRuntimeArnOutput79B88F18: arn:aws:bedrock-agentcore:us-east-1:227017984506:runtime/personalAgent_personalAgent-bpV5TVHepU
ApplicationMemoryIds538D889E: personalAgent_SharedMemory-2a20R7622q
ApplicationMemorySharedMemoryIdOutput00409E82: personalAgent_SharedMemory-2a20R7622q
StackNameOutput: AgentCore-personalAgent-default
Note: Transaction search enabled. It takes ~10 minutes for transaction search to be fully active and for traces from invocations to be indexed.
Next: agentcore invoke | agentcore status
Log: agentcore/.cli/logs/deploy/deploy-20260504-213717.log
(.venv) (py313) sagemaker-user@default:~/agentcore-runtime-quickstart/personalAgent$ agentcore cb versions --bundle NutritionControl --json
agentcore cb versions --bundle NutritionTreatment --json
Error: Configuration bundle "NutritionControl" not found. Has it been deployed?
Error: Configuration bundle "NutritionTreatment" not found. Has it been deployed?
(.venv) (py313) sagemaker-user@default:~/agentcore-runtime-quickstart/personalAgent$ agentcore status
AgentCore Status (target: default, us-east-1)
Agents
personalAgent: Deployed - Runtime: READY
(arn:aws:bedrock-agentcore:us-east-1:227017984506:runtime/personalAgent_personalAgent-bpV5TVHepU)
URL: https://bedrock-agentcore.us-east-1.amazonaws.com/runtimes/arn%3Aaws%3Abedrock-agentcore%3Aus-east-1%3A22701
7984506%3Aruntime%2FpersonalAgent_personalAgent-bpV5TVHepU/invocations
Memories
SharedMemory: Deployed (SEMANTIC, SUMMARIZATION, USER_PREFERENCE)
(arn:aws:bedrock-agentcore:us-east-1:227017984506:memory/personalAgent_SharedMemory-2a20R7622q)
Config Bundles
NutritionControl: Local only
NutritionTreatment: Local only
Expected Behavior
Config Bundles should have identifiers and been remotely deployed.
Actual Behavior
Config Bundles
NutritionControl: Local only
NutritionTreatment: Local only
CLI Version
1.0.0-preview.7
Operating System
macOS
Additional Context
No response
Description
agentcore add config-bundlesucceeds andagentcore deploy -ycompletes without error, but the deployed config bundles are never recognized by the service. Runningagentcore cb versions --bundle NutritionControlreturns Error: Configuration bundle "NutritionControl" not found. Has it been deployed?, andagentcore statusshows both bundles as "Local only" even after a successful deploy.Attempting to re-add the bundles with
--branchand--commit-messageflags then fails with "Configuration Bundle already exists," creating a dead-end where the bundles exist locally (blocking re-creation) but were never actually provisioned remotely (blocking version queries or A/B test usage).The root cause appears to be that agentcore deploy does not actually deploy config bundles to the service — it only deploys the runtime/memory infrastructure — leaving bundles stranded in local state with no CLI path to push them to the remote.
Steps to Reproduce
Expected Behavior
Config Bundles should have identifiers and been remotely deployed.
Actual Behavior
CLI Version
1.0.0-preview.7
Operating System
macOS
Additional Context
No response