Access Control
SSH Hardening
Section titled “SSH Hardening”Both servers are configured for SSH key authentication only. Password authentication is disabled.
Azure (az-apps-dev02)
Section titled “Azure (az-apps-dev02)”| Setting | Value |
|---|---|
| Allowed users | kaks |
| Password auth | Disabled |
| Root login | Disabled |
| Port | 22 |
Contabo (vmi2912133)
Section titled “Contabo (vmi2912133)”| Setting | Value |
|---|---|
| AllowUsers | root, pk, smallgod |
| Password auth | Disabled |
| Root login | Allowed (key only) |
| Port | 22 |
| Config file | /etc/ssh/sshd_config |
Service Access Levels
Section titled “Service Access Levels”| Service | Who Can Access | How |
|---|---|---|
| SSH (Azure) | kaks | SSH key |
| SSH (Contabo) | root, pk, smallgod | SSH key |
| Harbor | Team members with Harbor account | Web UI / Docker CLI |
| Portainer | Team members with Portainer account | Web UI |
| Keycloak Admin | Admins with master realm credentials | Web UI |
| RabbitMQ UI | Anyone with URL (no extra auth) | Web UI |
| docs.ayinza.dev | Team members | Basic auth (devops) |
Firewall
Section titled “Firewall”Currently, both servers have all ports open via cloud provider security groups/firewall. The only port-level restriction is Docker’s own service publishing — internal services are not exposed to the public internet.