* Add Market Trends Agent with Bedrock AgentCore browser integration
- Implements Strands-based agent for real-time stock data and business news
- Uses Bedrock AgentCore browser_client for web scraping
- Includes tools for Yahoo Finance stock data and Bloomberg news search
- Features professional market analysis with AI-powered insights
- Supports concurrent browser sessions for multiple stock comparisons
- Complete with tests, documentation, and clean requirements
* feat: Add Market Trends Agent with AgentCore integration
- Implement conversational broker card system with memory integration
- Add browser automation for real-time market data and news
- Create LangGraph-based agent architecture with tool orchestration
- Include deployment scripts and comprehensive documentation
- Add test scripts demonstrating broker profile workflow
- Configure Docker containerization for AgentCore Runtime
* feat: optimize memory management and fix deployment issues
- Fix memory creation to check existing memory first, eliminating ValidationException errors
- Extract memory tools into separate module for better organization
- Update deployment script with enhanced error handling and IAM permissions
- Add architecture documentation and diagrams
- Successfully deployed to burner account with Claude Sonnet 4 and multi-strategy memory
* fix: remove unsupported auto_update_on_conflict parameter and enable dynamic config
- Remove auto_update_on_conflict parameter from runtime.launch() call
- Allow .bedrock_agentcore.yaml to be generated dynamically by deploy script
- Successfully deployed to burner account (484363822803) with Claude Sonnet 4
- All tests passing: 4/4 (100% success rate)
- Agent fully functional with memory, market data, and news search capabilities
* fix:image link in readme
* fix:replaced image
* fix: resolve all linting errors and code quality issues
- Remove unused imports: tool, MemoryClient, ClientError, argparse, json, os, datetime, Any, re
- Fix f-strings without placeholders by converting to regular strings
- Remove unused variables: config_response, launch_result
- Clean up code to pass GitHub checks and improve maintainability
Fixes:
- deploy.py: 4 issues (f-strings + unused variables)
- market_trends_agent.py: 6 unused imports
- test_broker_card.py: 2 issues (unused import + f-string)
- tools/broker_card_tools.py: 2 unused imports
- tools/memory_tools.py: 3 issues (unused import + 2 f-strings)
* Changes to be committed:
modified: 02-use-cases/market-trends-agent/.gitignore
modified: 02-use-cases/market-trends-agent/tools/memory_tools.py
* fix: add back datetime import needed for session_id generation
The datetime import was accidentally removed but is still needed on line 27 for creating session IDs in the format 'market-{datetime.now().strftime('%Y%m%d%H%M%S')}'.
* refactor: remove Dockerfile from repo, let deployment auto-generate
- Remove Dockerfile from version control
- Add Dockerfile to .gitignore
- Deployment script will auto-generate Dockerfile with proper defaults
- Reduces repo clutter while maintaining deployment functionality
- Auto-generated Dockerfile will include necessary configurations
* Add uv support and fix news source reliability
- Add pyproject.toml with uv configuration
- Update README to use only uv commands
- Fix Reuters and CNBC URL issues with better error handling
- Add interactive chat instructions for users
- Improve browser tool with retry logic and reliable fallbacks"
* Fix memory management and add uv integration
- Fix broker identity confusion by enforcing identify_broker() workflow
- Improve actor_id consistency across memory operations
- Add enhanced error handling for news sources (Reuters/CNBC 503 errors)
- Add uv integration with pyproject.toml for faster dependency management
- Streamline README to uv-only workflow with interactive chat instructions
- Add reliable fallback news sources (Yahoo Finance, MarketWatch)
* Fix broker identification workflow and message filtering
- Enhanced system prompt to enforce mandatory broker identification
- Fixed tool_use/tool_result message pairing in filtering logic
- Added comprehensive test suite for broker memory storage
- Verified multi-strategy memory works for Tim Dunk and Maria Rodriguez
* Implement distributed memory coordination using SSM Parameter Store
- Added SSM Parameter Store for distributed memory ID coordination
- Enhanced race condition protection for deployment scenarios
- Updated IAM permissions to include SSM parameter access
- Prevents multiple memory instances during AgentCore deployment
- Maintains backward compatibility with local .memory_id file
* Add comprehensive cleanup script and documentation
- Created cleanup.py script to remove all deployed AWS resources
- Cleans up AgentCore runtime, memory, ECR, CodeBuild, S3, IAM, SSM
- Added safety features: dry-run mode, confirmation prompts, detailed logging
- Updated README with complete cleanup section and troubleshooting
- Tested cleanup successfully removes all resources except runtime (manual)
- Supports selective cleanup options (--skip-iam, --region, --dry-run)
* fix: resolve all lint errors in market trends agent
- Remove unused imports (json, time, extract_actor_id)
- Fix f-strings without placeholders in browser_tool.py
- Replace bare except clauses with specific exception handling
- Add proper logging for exception cases
- All files now pass ruff lint checks
---------
Signed-off-by: Erez Weinstein <125476602+erezweinstein5@users.noreply.github.com>
Co-authored-by: Erez Weinstein <erweinst@amazon.com>
* Add Ash, Dependabot, Lint check workflows for Pull Requests
* Fix ASH workflow: Use pip install and direct ash command
Based on official ASH documentation, the correct approach is:
1. Install ASH using pip (not uv tool)
2. Run ash command directly (not via uv tool run)
This follows the GitHub Actions example from the ASH documentation.
* Fix ASH workflow: Install scanner dependencies manually
- Install bandit, semgrep, detect-secrets, checkov via pip
- This ensures scanners run instead of being SKIPPED due to missing uv
* Update ASH security scan workflow with container mode and improved comment management
* Configure ASH container to show all security findings instead of limiting to 20
* Modify workflows to comment on runs
* Remove unused .ash.yaml configuration file
The ASH workflows create their own inline configurations and do not use this root config file
* add nova sonic agentcore integration sample
* nova sonic integration sample add integration architecture and tooluse json
* nova sonic integration sample add integration architecture and tooluse json
* nova sonic integration sample add integration architecture and tooluse json
* nova sonic integration sample add integration architecture and tooluse json
* nova sonic integration sample add integration architecture and tooluse json
* novs sonic integration remove best practies
---------
Co-authored-by: Lana Zhang <lanaz@amazon.com>
* Add Ash, Dependabot, Lint check workflows for Pull Requests
* Fix ASH workflow: Use pip install and direct ash command
Based on official ASH documentation, the correct approach is:
1. Install ASH using pip (not uv tool)
2. Run ash command directly (not via uv tool run)
This follows the GitHub Actions example from the ASH documentation.
* Fix ASH workflow: Install scanner dependencies manually
- Install bandit, semgrep, detect-secrets, checkov via pip
- This ensures scanners run instead of being SKIPPED due to missing uv
* Update ASH security scan workflow with container mode and improved comment management
* Configure ASH container to show all security findings instead of limiting to 20
* feat(memory): update tutorial to use Agent state
* feat(memory): update tutorial to use Agent state
* feat(memory): update tutorials to use state
* feat(memory): update tutorials to use agent State
* Add Enterprise Web Intelligence Agent with Bedrock AgentCore Tools SDK
Automated browser navigation with CDP enhancements
Live viewing with DCV integration
Session recording and replay capabilities
LLM-powered content extraction
Code Interpreter for dynamic analysis
Comprehensive documentation and examples
* Moved project from old-folder to new-folder and updated files
* Refactor: Rename to enterprise-web-intelligence-agent and add Strands implementation alongside LangGraph
* enhanced the database analysis functionalities and updated the database setup not to store secret name in config
* Security fix: Remove sensitive data from config files, use SSM Parameter Store
* cleanup files
* Create CONTRIBUTORS.md
Signed-off-by: David L. <32494274+architec@users.noreply.github.com>
* Create CONTRIBUTORS.md and add all contributors
Signed-off-by: David L. <32494274+architec@users.noreply.github.com>
---------
Signed-off-by: David L. <32494274+architec@users.noreply.github.com>
- Fixed socket binding to use 127.0.0.1 instead of all interfaces
- Improved error handling to prevent stack trace exposure
- Additional security improvements
* updated README.md file with bearer token generation
* updated README.md file with bearer token generation-removed client id and secret credentials
* removed hardcoded domain
* added agent runtime, frontend, observability and agentcore identity
* update README.md file to reflect frontend testing
* fixed Client-side cross-site scripting and DOM text reinterpreted as HTML
* fixed Client-side cross-site scripting and DOM text reinterpreted as HTML
* • Upgrading from the vulnerable version 3.3.0 to the patched version 3.4.0
• Fixing the algorithm confusion vulnerability with OpenSSH ECDSA keys (similar to CVE-2022-29217)
• Resolving the 2 Dependabot alerts mentioned in the pull request
* updated README.md file with bearer token generation
* updated README.md file with bearer token generation-removed client id and secret credentials
* removed hardcoded domain
* added agent runtime, frontend, observability and agentcore identity
* update README.md file to reflect frontend testing
* fixed Client-side cross-site scripting and DOM text reinterpreted as HTML
* fixed Client-side cross-site scripting and DOM text reinterpreted as HTML
Notes:
- AgentCore Gateway today only supports MCP Protocol version 2025-03-26.
- MCP protocol version support only starts after mcp>=1.9.0 so adding it as a requirement.
Testing:
- Created new venv and installed all requirements according to requirements.txt
- Started the MCP S3 agentcore gateway notebook and it was able to run successfully.
Co-authored-by: Tejas Dastane <tdastan@amazon.com>
