AWS bedrock-agentcore documentation change
Summary
Added a Topics section for navigation and made minor typographical changes.
Security assessment
The changes are about improving documentation structure and fixing typographical issues, with no evidence of addressing a security issue or adding security documentation. The added navigation links and typographical fixes do not alter the security content or indicate a response to a security vulnerability.
Diff
diff --git a/bedrock-agentcore/latest/devguide/code-interpreter-session-characteristics.md b/bedrock-agentcore/latest/devguide/code-interpreter-session-characteristics.md index 17fa341c7..a77ba46f3 100644 --- a//bedrock-agentcore/latest/devguide/code-interpreter-session-characteristics.md +++ b//bedrock-agentcore/latest/devguide/code-interpreter-session-characteristics.md @@ -21 +21 @@ Session persistence -Files and data created during a session are available throughout the session's lifetime. When the session is terminated, the session no longer persists and the data is cleaned up. +Files and data created during a session are available throughout the session’s lifetime. When the session is terminated, the session no longer persists and the data is cleaned up. @@ -37,0 +38,15 @@ The time to live (TTL) retention policy for the session data is 30 days. +###### Topics + + * Using isolated sessions + + * [Starting a AgentCore Code Interpreter session](./code-interpreter-start-session.html) + + * [Executing code](./code-interpreter-execute-code.html) + + * [Runtime selection](./code-interpreter-runtime-selection.html) + + * [Stopping a AgentCore Code Interpreter session](./code-interpreter-stop-session.html) + + + + @@ -42 +57 @@ AgentCore Tools enable isolation of each user session to ensure secure and consi -Each tool session runs in a dedicated microVM with isolated CPU, memory, and filesystem resources. This architecture guarantees that one user's tool invocation cannot access data from another user's session. Upon session completion, the microVM is fully terminated, and its memory is sanitized, thereby eliminating any risk of cross-session data leakage. +Each tool session runs in a dedicated microVM with isolated CPU, memory, and filesystem resources. This architecture guarantees that one user’s tool invocation cannot access data from another user’s session. Upon session completion, the microVM is fully terminated, and its memory is sanitized, thereby eliminating any risk of cross-session data leakage.