Diagnostics

Exactly what MAX is connected to, and what it is still waiting on.

Connection diagnostics

Raw probes. Token values are never printed — only presence, claims and expiry.

Auth status

isAuthenticatedfalse

ID token present (HTTP Bearer)false

Access token present (WebSocket)false

Stored expirynot reported

ID token exp claimnot reported

ID token token_usenot decoded

ID token issnot decoded

Access token exp claimnot reported

Access token token_usenot decoded

Access token scope claim presentfalse

Expected issuerhttps://cognito-idp.us-east-1.amazonaws.com/us-east-1_hNqcpSXTo

Issuer matches expectedfalse

Cognito client id37pj7s1u2oh6b71of4c2t06l49

Token aud / client_idnot decoded

Current originserver render

Redirect URI used/auth/callback

Logout URI usedhttps://maxwell-core-575108920285.auth.us-east-1.amazoncognito.com/logout?client_id=37pj7s1u2oh6b71of4c2t06l49&logout_uri=%2Fauth%2Fcallback

Origin on CORS allowlist (client-side belief)false

HTTP endpoint results

Run the probes to populate this section.

WebSocket

Configured URLwss://urxuu3bcbe.execute-api.us-east-1.amazonaws.com/$default

Includes /$defaulttrue

Auth methodCognito ACCESS token as ?token= query param

Query paramstoken=<redacted>

First outbound payload shape{"action":"sendMessage","conversation_id":"<string>","text":"<string>"}

Live transport state (app socket)closed

Probe openednot run

Probe ms to openn/a

Close codenot run

Close reasonnot run

wasCleannot run

error event firednot run

Inbound framesnone

Probe note—

WebSocket handshake attempts (0)

No handshake attempted yet in this session. Sign in or run the probes to populate this log.

HTTP APIhttps://49qdet1uz4.execute-api.us-east-1.amazonaws.com

Health path/health

Health resultpending

Roster path/roster

Alerts path/alerts

Missions path/missions

Control path/control

Activity pathno backend route (client-side grouping)

WebSocketwss://urxuu3bcbe.execute-api.us-east-1.amazonaws.com/$default

Socket authaccess token as ?token= query param

HTTP authAuthorization: Bearer <ID token>

Cognito user poolus-east-1_hNqcpSXTo

Cognito client37pj7s1u2oh6b71of4c2t06l49

Hosted UImaxwell-core-575108920285.auth.us-east-1.amazoncognito.com

Callback URI (this origin)/auth/callback

IdentitySigned out

TransportSocket closed

Derived MAX stateoffline

Deployed app originhttps://d29gjpfza3a43t.cloudfront.net

Backend work still required

This origin is not on the Maxwell CORS allowlist

The HTTP API allows only https://d29gjpfza3a43t.cloudfront.net. Browser CORS will block every call from this origin until it is added to CorsConfiguration.AllowOrigins in MaxwellCoreControlPlaneV1.template.yaml and redeployed.

This origin's callback URL is not registered in Cognito

Add /auth/callback to CallbackURLs and LogoutURLs on app client 37pj7s1u2oh6b71of4c2t06l49. Until then Cognito rejects the sign-in redirect.

No backend /activity route exists

Confirmed by the contract: Activity is a client-side grouping of /alerts, /control and /push/subscriptions — not a backend endpoint.

Voice upload route is not implemented server-side

/audio-upload-url is referenced by the legacy frontend but no route or Lambda implements it. MAX does not build against it.