Arvados

This might be as simple as one misconfiguration, but if you take our current compute node build script and try to build an image on top of a Debian 12 AMI, it never manages to SSH in to start the build work. This error repeats until it gives up:

2024/10/18 01:27:58 packer-builder-amazon-ebs plugin: Using host value: 54.175.47.1
2024/10/18 01:27:58 packer-builder-amazon-ebs plugin: [INFO] Attempting SSH connection to 54.175.47.1:22...
2024/10/18 01:27:58 packer-builder-amazon-ebs plugin: [DEBUG] reconnecting to TCP connection for SSH
2024/10/18 01:27:58 packer-builder-amazon-ebs plugin: [DEBUG] handshaking with SSH
2024/10/18 01:27:58 packer-builder-amazon-ebs plugin: [DEBUG] SSH handshake err: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2024/10/18 01:27:58 packer-builder-amazon-ebs plugin: [DEBUG] Detected authentication error. Increasing handshake attempts.
==> amazon-ebs: Error waiting for SSH: Packer experienced an authentication error when trying to connect via SSH. This can happen if your username/password are wrong. You may want to double-check your credentials as part of your debugging process. original error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

I've checked that admin is still the correct username at least.