AWS bedrock-agentcore documentation change
Summary
Updated documentation links from 'runtime-persistent-filesystems.html' to 'runtime-filesystem-configurations.html' for session storage persistence references
Security assessment
The changes only update hyperlink references and remove the '(Preview)' label. There is no mention of vulnerabilities, security patches, or new security controls. The content about persistent storage remains functionally identical.
Diff
diff --git a/bedrock-agentcore/latest/devguide/runtime-sessions.md b/bedrock-agentcore/latest/devguide/runtime-sessions.md index 07f0210c5..52dd93372 100644 --- a//bedrock-agentcore/latest/devguide/runtime-sessions.md +++ b//bedrock-agentcore/latest/devguide/runtime-sessions.md @@ -51 +51 @@ By default, the compute (microVM) associated with a session is ephemeral. Any da -To persist filesystem data across session stop/resume cycles, configure **session storage** — a persistent directory that survives compute termination. See [Persist session state across stop/resume with a filesystem configuration (Preview)](./runtime-persistent-filesystems.html). +To persist filesystem data across session stop/resume cycles, configure **session storage** — a persistent directory that survives compute termination. See [File system configurations for AgentCore Runtime](./runtime-filesystem-configurations.html). @@ -73 +73 @@ Session state is determined by the compute lifecycle and can be one of the follo - * **Stopped** : The compute (microVM) provisioned for the session has been terminated and the session is stopped. This can occur due to inactivity (default 15 minutes), reaching max compute lifetime (default 8 hours), an explicit stop by invoking the [StopRuntimeSession](https://docs.aws.amazon.com/bedrock-agentcore/latest/APIReference/API_StopRuntimeSession.html) API, or if the compute is deemed unhealthy based on health checks. The session transitions back to Active on the next invocation and a new compute is provisioned, with the same lifecycle configuration (i.e. idleRuntimeSessionTimeout and maxLifetime that can be up to another 8 hours). The session itself remains valid until the AgentCore Runtime ARN is deleted. If the runtime is configured with session storage, filesystem data at the configured mount path persists across stop/resume cycles. See [Persist session state across stop/resume with a filesystem configuration (Preview)](./runtime-persistent-filesystems.html). + * **Stopped** : The compute (microVM) provisioned for the session has been terminated and the session is stopped. This can occur due to inactivity (default 15 minutes), reaching max compute lifetime (default 8 hours), an explicit stop by invoking the [StopRuntimeSession](https://docs.aws.amazon.com/bedrock-agentcore/latest/APIReference/API_StopRuntimeSession.html) API, or if the compute is deemed unhealthy based on health checks. The session transitions back to Active on the next invocation and a new compute is provisioned, with the same lifecycle configuration (i.e. idleRuntimeSessionTimeout and maxLifetime that can be up to another 8 hours). The session itself remains valid until the AgentCore Runtime ARN is deleted. If the runtime is configured with session storage, filesystem data at the configured mount path persists across stop/resume cycles. See [File system configurations for AgentCore Runtime](./runtime-filesystem-configurations.html).