👋 Welcome! We're glad you're interested in the Bedrock AgentCore SDK Python.
This repository is maintained exclusively by the AWS Bedrock AgentCore team and is not currently accepting external pull requests.
While we appreciate your interest in contributing code, we maintain this policy to:
- Ensure code quality and security standards
- Maintain consistency with internal AWS development practices
- Align with our product roadmap and architecture decisions
- Comply with AWS security and compliance requirements
# Clone the repository
git clone https://github.com/aws/bedrock-agentcore-sdk-python.git
cd bedrock-agentcore-sdk-python
# Create virtual environment and install dependencies
uv venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
uv sync
# Install pre-commit hooks (one-time)
pre-commit installThat's it! You're ready to develop.
Pre-commit hooks will now run automatically:
# Make your changes
vim src/bedrock_agentcore/myfile.py
# Commit (hooks run automatically)
git commit -m "feat: add new feature"
# ↑ Formatting and linting run here
# Push (tests run automatically)
git push origin my-branch
# ↑ Security scanning and tests run hereOn every commit (~10-20 seconds):
- ✅ Code formatting (auto-fixes with ruff)
- ✅ Import sorting (auto-fixes)
- ✅ Linting (with ruff)
- ✅ File hygiene (trailing whitespace, etc.)
Before every push (~2-5 minutes):
- ✅ Security scanning (bandit)
- ✅ Full test suite with coverage
For work-in-progress commits, you can skip checks:
git commit --no-verify -m "wip: incomplete work"Please run all checks before opening a PR!
# Run all pre-commit checks
pre-commit run --all-files
# Run only pre-commit stage (fast)
pre-commit run --hook-stage pre-commit --all-files
# Run only pre-push stage (includes tests)
pre-commit run --hook-stage pre-push --all-files
# Run tests manually
uv run pytest tests/ --cov=srcAlthough we don't accept code contributions, your feedback is invaluable! Here's how you can help improve the SDK:
Found something that doesn't work as expected? Please open an issue with:
- A clear description of the problem
- Steps to reproduce the issue
- Expected vs actual behavior
- Environment details (OS, Python version, SDK version)
- Relevant code snippets and error messages
Have an idea for a new feature? Please open a feature request with:
- Description of the problem you're trying to solve
- Proposed solution or feature
- Use cases and examples
- Any alternative solutions you've considered
Spot an error or unclear explanation in our docs? Please open a documentation issue with:
- Link to the documentation page
- Description of the issue or improvement
- Suggested changes (if applicable)
While we can't accept code PRs, we'd love to hear about your use cases:
- Open a "Show and Tell" discussion in our Discussions forum
- Share your experience and learnings
- Help other users with questions
When creating an issue:
- Search first: Check if a similar issue already exists
- Use templates: Select the appropriate issue template
- Be specific: Provide as much detail as possible
- Stay on topic: Keep discussions focused on the issue
- Be respectful: Follow our Code of Conduct
For security vulnerabilities, please DO NOT open a public issue. Instead:
- Email: aws-security@amazon.com
- Or use GitHub's private security advisory feature
See our Security Policy for more details.
- For questions about using the SDK, please use GitHub Discussions
- For AWS Bedrock service questions, visit AWS re:Post
- For urgent AWS support, use your AWS Support plan
This project adheres to the Amazon Open Source Code of Conduct. By participating, you're expected to uphold this code.
This project is governed by the AWS Bedrock AgentCore team. Decisions about the project's direction, features, and releases are made internally by AWS.
By engaging with this project, you agree that your contributions (issues, discussions, etc.) are submitted under the Apache 2.0 License.
Even though we can't accept code contributions at this time, your feedback, bug reports, and feature requests help us make the Bedrock AgentCore SDK better for everyone. We truly appreciate your involvement and support!
Note: This policy may change in the future. If we open the repository to external contributions, we'll update this document and announce the change.