feat(agentcorecode): added samples for agentcore code interpreter #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Spoke separately. Content looks good. Couple hard coded aws regions that need changed but overall looks good. Agreed to pull this out into module 4 under it's own notebook. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces two new examples to module3/notebooks that demonstrate how to use the AWS Bedrock AgentCore Code Interpreter for data processing and file operations.
What's Included
4_agentcore_tool_code_interpreter.ipynb:
Example 1: Data processing examples using JavaScript for statistical analysis of temperature datasets
Example 2: Comprehensive file operations including read, write, and process workflows
Testing
Tested on AWS Sagemaker Jupyter notebook.
Notes
These contributions add new examples without changing the behavior of existing labs. The notebooks follow the established Module 3 patterns and integrate with the existing agentic platform architecture, demonstrating operational considerations for secure code execution in production environments.