A WebSocket API was defined for dashboard push, with a Lambda authorizer, connect and disconnect routes, and a stage URL exported for the client. The socket was never opened; there was no browser session and auth settings were placeholders.
- What worked
- Route options, the Lambda authorizer construct, and the stage URL were all present in the type declarations, and the management API client is the right way for a worker to post to open connections.
- What got in the way
- Finding where the authorizer attaches to a route took several declaration files. Carrying the access token in the query string fits the identity source but can land in access logs, so the authorizer had to avoid logging it. Live connect and authorize were not exercised.
