AgentCore live previews make port scope a release decision

AWS Session endpoints let teams inspect apps inside an agent's runtime without a separate deploy. Their authenticated URLs still expose every allowed port in the same session, so preview access needs deliberate limits.
On 30 October, AWS showed a coding agent serving a live Vite site from an Amazon Bedrock AgentCore runtime session while it edits files. Session endpoints provide an authenticated URL for HTTP and WebSocket access to selected ports. The useful change is faster review, but the control question is which services a reviewer can reach inside that agent session.
AWS says each runtime session runs in its own microVM. A Session endpoint forwards requests only to ports listed in the runtime's allowedPorts configuration. Its sample exposes a web preview on port 8090 and a status route on 8081; the agent's invocation port is reached through a separate API. That distinction should be explicit in a team's deployment design.
Authentication is attached to every request
The URL alone does not grant access. AWS says each HTTP request and WebSocket handshake needs a SigV4 signature and InvokeAgentRuntimeProxy permission, or a bearer token for a JWT-authorised runtime. The client also checks the requested port. In the sample, requests without credentials or to an unapproved port are refused.
A browser cannot sign the preview's own requests, so the AWS SDK opens a local endpoint that adds credentials before forwarding them. That helper listens on the user's loopback interface in the example. Operators should treat it as a temporary access bridge and stop it when review ends, rather than turning it into a standing shared service.
The preview URL is a doorway to allowed services in the agent's session.
The shared session remains the boundary
The preview app and coding agent run inside the same session. AWS notes that Session endpoint access controls do not separate the website from the agent. An allowed website port does not make arbitrary agent files safe to serve; the execution role and file tools still need narrow permissions. The sample's file tools resolve paths inside the site folder and refuse paths outside it.
The endpoint is also a development path, not production hosting. Its URL lasts only while the session exists, and AWS advises deploying user-facing applications to a hosting service. The live preview can prove that a page renders during editing, but it is not evidence that the build is reviewed, durable or ready for public traffic.
Test the refused paths
A practical acceptance test should request an allowed port with valid credentials, then repeat without credentials and against a port outside allowedPorts. Confirm the expected refusals and check CloudTrail records for InvokeAgentRuntimeProxy activity. Test WebSocket access as well, because a live reload channel is part of the preview path.
Before promoting code, review the agent's edits and move the resulting app through the normal build and deployment pipeline. Session endpoints shorten the feedback loop for reviewers. Their security value depends on tight port selection, short lived access and a clear separation between preview and publication.
Sources
Written by the Devence Lab research team.




