Inspect History in the Kam State console
Kam State adds versioned application state to Amazon Bedrock AgentCore.
Review an AgentCore workload’s recorded evidence in the read-only Kam State console, across every property and client app your account can read, without building a separate inspection interface.
Guide context
Inspect Kam State History from an Amazon Bedrock AgentCore workload in the read-only Kam State console. Sign in, choose an organization, property and client app, then navigate workspace, scope, date and exact revision.
Inspect the State History an AgentCore application recorded in Kam State. Sign in, choose an organization, property and client app, then navigate workspace, scope, UTC date and exact revision read-only. An old version is never replaced with a newer one. Live service configuration, identity and workspace authority require separate qualification.
On this page · 4 sections
Inspect an AgentCore workload's History
Sign in and choose a client app
Pick the organization, property and client (iOS, Android, Mobile, Web or macOS) whose authorized workspace you need.
Choose workspace and scope
Use the server-authorized workspace and supplied subject and type.
Pin UTC day and generation
Keep membership fixed while reading more pages.
Inspect the exact revision
Read retained data and source references; the console executes no agent or tool.
Browse History like folders#
Workspaces
The History API lists the workspaces your account may read, with your role.
Scope
Enter the subject and record type supplied for your authorized workspace. The console does not invent a scope directory.
UTC days
Pick a month, then select today or one of the preceding 364 UTC dates. A date in this window is eligible for reads; its presence does not mean that the day’s records are complete.
Exact records
One page of a pinned generation is hydrated to exactly those revisions; the inspector adds timestamps, source references, and the record’s earlier revisions.
Sign in and sign out#
Open /console. Without a session you are sent to /console/sign-in, which keeps the view you asked for and returns you there after sign-in. Only console and Kam Sports paths on this site are accepted as a return destination. The console uses the Cognito client’s configured Amplify sign-in flow, including SMS, email, authenticator and new-password challenges. Server settings choose email or username; they do not grant workspace access.
The server reads the session, re-verifies the Cognito access token with AWS’s verifier, and calls the History API on your behalf. Which workspaces you see comes from the History API, never from the browser; a refusal is shown as access denied, never worked around.
Sign out from Account and help. The browser’s Amplify session and the server cookie are cleared, every loaded History view is discarded, and you land on /console/sign-out. Visiting that page while signed in shows an explicit Sign out action; rendering it never signs anyone out. An expired session ends the same way and offers Sign in to return to the same view.
Organizations, properties and client apps#
Client toggles choose which authorized workspace you inspect. They do not enable, disable or reconfigure an app, and they do not change who can read it. Workspace owners manage access in the History service.
Organization
A customer account, such as one company with several products. If your account can read more than one organization, choose it at the top of Organizations.
Property
One product or website within the organization, for example a web app and its companion mobile apps. Each property card lists only the clients your account can read.
Client app
iOS, Android, Mobile, Web or macOS. Each client maps to an authorized workspace. Toggle a client on a property card, or use Show client to see the same client across every property, then open its History.
Access
The History API’s workspace directory is the only source of access. An operator catalog names and groups those workspaces; it cannot add one. Workspaces without a label are still listed under Other workspaces.
What the console will not do#
Write anything
Only read routes are called. There is no outcome, configuration, deletion, or lifecycle action, and client toggles change no app or access setting.
Fall back to latest
A changed generation or a revision that does not match the requested reference is an error, not a substitution.
Read without bounds
At most 32 references per read, only inside the 365-UTC-date window, and never a cursor without its generation.