@kamil for changes related to data clearance. I didn't add him as a blocking reviewer since he might be absent for a longer time. But if he is back quickly I would appreciate his review on the data clearance.

Requesting changes to fix failing CI - most likely wrong uuid version is being resolved, try the yarn why uuid command to confirm.

Apply review feedback

In D9165#270046, @michal wrote:

Would it make sense to add apply_immediately (at least for staging)? If I understand the documentation correctly, currently if we make changes to the user (or add broker configuration) we would have to reboot rabbitmq manually?

This health check is only needed by AWS to check if the instance endpoint is healthy. It's more related to ENG-4470.

In D9156#269886, @michal wrote:

Is generic-ness of this is going to be helpful in the future? Or is it going to be always HyperWebsocket under the hood? Because in that case we should just remove the generics and use HyperWebsocket directly

Update port in docker-compose

In D9139#269877, @michal wrote:

Should we also update the docker-compose.yml to use the new port?

Nice! The UI change looks good to me, but letting others review as well.

Use separate tag for staging, bump prod version

In D9158#269711, @ashoat wrote:

Awesome that we get the health check for free! I assume we'll need to implement something on the client for that to work, yes? The Tunnelbroker client in keyserver currently uses the ws library for Node.js

In D9142#269446, @atul wrote:

What's the command to run tests? Can they be run without any additional configuration?

Taking this one, I'll play with this a bit