AWS bedrock-agentcore documentation change
Summary
Clarified that sessions can persist beyond instance termination with new instances provisioned, and updated documentation about session termination behavior.
Security assessment
This change provides clarification about runtime lifecycle behavior and session persistence. There's no evidence of security implications or security-related documentation being added. The changes appear to be routine documentation updates for better clarity about system behavior.
Diff
diff --git a/bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md b/bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md index 985f18226..94de3aa3f 100644 --- a//bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md +++ b//bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md @@ -39 +39 @@ Lifecycle configuration attributes Attribute | Type | Range (seconds) | Required -`maxLifetime` | Integer | 60-28800 | No | Maximum lifetime for the instance in seconds. Once reached, instances will initialize termination. Termination can last up to 15 seconds due to logging and other process completion. Default: 28800 seconds (8 hours) +`maxLifetime` | Integer | 60-28800 | No | Maximum lifetime for the instance in seconds. Once reached, instances will initialize termination. Termination can last up to 15 seconds due to logging and other process completion. Default: 28800 seconds (8 hours). The session itself can persist beyond this with a new instance provisioned. @@ -273 +273 @@ Key points about lifecycle settings and sessions: - * **Session termination** : When either timeout is reached, only that specific session's microVM is terminated + * **Session termination** : When either timeout is reached, only that specific session's microVM is terminated. The session can be resumed with a new microVM provisioned.