Getting Access

Prerequisites

Before you can operate the SSERIS platform, you’ll need:

1. SSH key pair — your public key must be added to the server’s authorized_keys
2. VPN access — not required (WireGuard runs server-to-server, not client-to-server)
3. Harbor credentials — for pushing/pulling container images
4. GitHub access — member of the ayinza and/or sseris organizations

SSH Access

Azure — az-apps-dev02

ssh kaks@4.180.181.86

• User: kaks (sudo access)
• Auth: SSH key only
• Manages: DEV stack, Nginx, stack files

Contabo — vmi2912133

ssh pk@84.247.134.135
ssh root@84.247.134.135

• Users: root, pk, smallgod
• Auth: SSH key only (password disabled)
• Manages: UAT, Shared, Harbor, runners

Caution

Contabo has AllowUsers configured in /etc/ssh/sshd_config. Only root, pk, and smallgod can SSH in. To add a new user, you must update this file and restart sshd.

Adding a New User’s SSH Key

1. Get their public key (e.g., id_ed25519.pub)
2. SSH into the server as an existing user
3. Add the key to the target user’s ~/.ssh/authorized_keys
4. On Contabo, ensure the username is in AllowUsers in /etc/ssh/sshd_config
5. Restart SSH: sudo systemctl restart sshd

Tool Access

Tool	URL	How to Get Access
Harbor	https://harbor.ayinza.dev	Admin creates account in Harbor UI
Portainer	https://portainer.swarm.ayinza.dev	Admin creates account in Portainer UI
Keycloak (DEV)	https://auth.swarm.ayinza.dev	Admin realm → add user
Keycloak (UAT)	https://auth.ayinza.dev	Admin realm → add user
GitHub	github.com/ayinza, github.com/sseris	Org admin sends invite

First Steps After Getting Access

1. SSH into both servers and verify you can connect
2. Run docker node ls to verify the Swarm is healthy
3. Run docker service ls to see all running services
4. Log into Harbor and Portainer to verify web UI access
5. Read the Common Commands page