The Bedrock AgentCore Starter Toolkit is a Python CLI toolkit designed to simplify the deployment of AI agents to Amazon Bedrock AgentCore Runtime. It enables developers to take Python-based agent logic (e.g., built with Strands Agents or LangGraph) and deploy it to AWS with minimal infrastructure management. The library is currently at version 0.3.5 and undergoes rapid development with frequent patch releases. While still active for existing Python workflows, AWS now recommends using the `@aws/agentcore-cli` (an npm-based CLI) for new projects due to its broader framework support and features.
pip install bedrock-agentcore-starter-toolkit==0.3.5Verified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to define a simple AI agent using `bedrock_agentcore.runtime.BedrockAgentCoreApp` and then deploy it using the `agentcore` command-line interface provided by the `bedrock-agentcore-starter-toolkit`. The Python code defines the agent's logic, which the CLI toolkit then containerizes and deploys to the AWS Bedrock AgentCore Runtime. Ensure your AWS credentials are configured (e.g., using `aws configure`) and you have the necessary IAM permissions to create roles, Lambda functions, and use Bedrock AgentCore services.
For new projects, consider installing and using the `@aws/agentcore-cli` via `npm i @aws/agentcore-cli`. Refer to the official AgentCore CLI documentation for migration guides if you need to move an existing project.
Review the `CHANGELOG.md` or release notes before updating to new versions, and thoroughly test your deployments after any updates.
Ensure your AWS CLI is configured (`aws configure`) and the IAM role used for deployment has policies allowing `bedrock:*`, `iam:*`, `ecr:*`, and `lambda:*` actions, especially `bedrock-agentcore:*` for runtime operations. Specify the `--region` argument during `agentcore configure` if not using your default AWS region.
Explicitly activate a supported Python version (e.g., Python 3.11), uninstall Python 3.13 if present, and ensure Python 3.11 paths are prioritized in environment variables, or use WSL (Windows Subsystem for Linux) for a more stable environment.
Manually delete the stale `bedrock_agentcore` section or the entire `.bedrock_agentcore.yaml` configuration file to force the toolkit to create a new agent and corresponding ID.
Ensure that workspace members containing agent code are correctly configured, and that the build context for `agentcore launch` includes the necessary package directories for `uv pip compile` to properly install local workspace packages.
Upgrade your `boto3` library to the latest version (`pip install --upgrade boto3`) and verify that your AWS IAM role has the required S3 permissions for bucket operations, or consider using the `--local-build` flag if S3 direct access is not intended for builds.
Attach the required IAM policies (e.g., `AmazonBedrockFullAccess`, `AmazonEC2ContainerRegistryFullAccess`) to your user/role, or explicitly grant `bedrock-agentcore:CreateAgentRuntime` permission, and ensure the agent's execution role has a trust policy allowing `bedrock-agentcore.amazonaws.com` to assume it.