AWS bedrock-agentcore documentation change
Summary
Added operational guidance for long-running agents, clarified health check responses, and added troubleshooting section
Security assessment
Changes focus on reliability and operational best practices rather than security vulnerabilities. The warning about blocking operations addresses availability concerns but doesn't indicate a security flaw.
Diff
diff --git a/bedrock-agentcore/latest/devguide/runtime-long-run.md b/bedrock-agentcore/latest/devguide/runtime-long-run.md index 9a4dd5d5d..2a8f3470c 100644 --- a//bedrock-agentcore/latest/devguide/runtime-long-run.md +++ b//bedrock-agentcore/latest/devguide/runtime-long-run.md @@ -5 +5 @@ -Key conceptsImplementing asynchronous tasksComplete example +Key conceptsImplementing asynchronous tasksComplete exampleCommon issues and solutions @@ -30 +30 @@ The Amazon Bedrock AgentCore SDK supports both synchronous and asynchronous proc -Agent code communicates its processing status using the "/ping" health status. "HealthyBusy" indicates the agent is busy processing background tasks, while "Healthy" indicates it is idle (waiting for requests). A session in idle state for 15 minutes gets automatically terminated. +Agent code communicates its processing status using the "/ping" endpoint health status. 200 HTTP Status response with payload `{"status": "HealthyBusy"}` indicates the agent is busy processing background tasks. `{"status": "Healthy"}` indicates it is idle (waiting for requests). A session in idle state for 15 minutes gets automatically terminated. @@ -39 +39,4 @@ To get started, install the `bedrock-agentcore` package: -### API based task management +AgentCore SDK provides following options for integration asynchronous processing. + +API based task management + @@ -52,24 +55 @@ To build interactive agents that perform asynchronous tasks, you need to call `a -### Asynchronous task decorator - -The Amazon Bedrock AgentCore SDK helps with tracking asynchronous tasks. You can get started by simply annotating your asynchronous functions with `@app.async_task`. - - - # Automatically track asynchronous functions: - @app.async_task - async def background_work(): - await asyncio.sleep(10) # Status becomes "HealthyBusy" - return "done" - - @app.entrypoint - async def handler(event): - asyncio.create_task(background_work()) - return {"status": "started"} - -Here is how it works: - - * The `@app.async_task` decorator tracks function execution - - * When the function runs, ping status changes to "HealthyBusy" - - * When the function completes, status returns to "Healthy" - +Custom ping handler @@ -78,3 +57,0 @@ Here is how it works: - -### Custom ping handler - @@ -98,0 +76,4 @@ Status values: +###### Important + +Ensure `@app.entrypoint` handler does not perform blocking operations, as this might also block the /ping health check endpoint. Use separate threads or async methods for blocking operations. + @@ -157,0 +139,13 @@ This example demonstrates: +## Common issues and solutions + +### Long-running agent gets terminated after 15 minutes + +This can happen when the application is single threaded and the ping thread is blocked. + + * Check that blocking calls in the invocation path are in a separate thread or async non-blocking + + * Run async agent server locally and simulate scenarios while checking for ping status. + + + +