AWS bedrock-agentcore documentation change
Summary
Formatting changes to table headers and typographical fixes in lifecycle settings documentation
Security assessment
Changes involve removing redundant column headers from tables (like 'Lifecycle configuration attributes' and 'Default behavior logic') and typographical fixes (straight quotes to curly quotes). No security implications are present as these are documentation formatting improvements without altering security guidance about session timeouts or microVM termination.
Diff
diff --git a/bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md b/bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md index 94de3aa3f..9d677c49d 100644 --- a//bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md +++ b//bedrock-agentcore/latest/devguide/runtime-lifecycle-settings.md @@ -36 +36 @@ You can also configure lifecycle settings for an existing AgentCore Runtime with -Lifecycle configuration attributes Attribute | Type | Range (seconds) | Required | Description +Attribute | Type | Range (seconds) | Required | Description @@ -56 +56 @@ When `LifecycleConfiguration` is not provided or contains null values, the platf -Default behavior logic Customer Input | idleRuntimeSessionTimeout | maxLifetime | Result +Customer Input | idleRuntimeSessionTimeout | maxLifetime | Result @@ -273 +272 @@ Key points about lifecycle settings and sessions: - * **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. + * **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. @@ -305 +304 @@ Follow these best practices when configuring lifecycle settings for optimal reso -Common configuration patterns Use Case | Idle Timeout | Max Lifetime | Rationale +Use Case | Idle Timeout | Max Lifetime | Rationale