Amazon Bedrock AgentCore Runtime Introduces Session Endpoints for Live Web App Previews
AI assistants · AI coding
AWS detailed Session endpoints for the Amazon Bedrock AgentCore runtime, allowing developers to preview web apps directly as coding agents build them in isolated microVMs. The feature exposes authenticated URLs forwarding HTTP, HTTP/2, and WebSocket traffic to user-defined ports, enabling real-time hot-reloading reviews without remote redeployment.
AWS detailed how Amazon Bedrock AgentCore runtime uses Session endpoints to provide live previews of web applications created by autonomous coding agents. Each agent session executes in an isolated microVM. By assigning an authenticated URL to the session, Session endpoints route HTTP methods, paths, query strings, bodies, and WebSocket connections to designated ports (between 8000 and 12000) configured during runtime creation. This enables local development loops—such as Vite hot-reloading—to reflect code changes in the browser within seconds without requiring external deployment. Requests are authenticated via AWS IAM Signature Version 4 or inbound JWT authorizers.
Key takeaways
- Amazon Bedrock AgentCore runtime executes agent sessions in isolated microVMs, with Session endpoints exposing authenticated URLs for direct browser interaction.
- Developers can configure 1 to 5 allowed ports or ranges within 8000–12000, supporting HTTP/1.1, HTTP/2, server-sent events, gRPC, and WebSocket connections.
- Authentication is enforced per request using AWS IAM SigV4 or inbound JWT authorizers, ensuring session URLs cannot be accessed anonymously.
- The walkthrough sample uses Claude Haiku 5.5 and a Vite development server to push live code modifications back to the preview interface without browser refreshes.
Source：AWS Machine Learning Read the original ↗
Prepared, checked and automatically published by AI; not individually reviewed by a human.