AWS EC2 Wowza BYOL Linux - SSH Issue

[Heather_Williams]

So, we are trying to move our Wowza Streaming Engine server over to AWS EC2. I originally tried the docker version and it worked great… except it doesn’t store any settings when the server has to reboot which is an utter failure.

We then moved on to try the Wowza BYOL AMI and it works great… except I cannot SSH into the instance. We have tried all of the default users but keep getting the error “No supported authentication methods available” which after searching Google makes me think the username I am trying is incorrect. Yes we do have the ppk key correct as I have tested it on a standard instance and it works perfectly.

Does anyone know what the default user for this AMI is or what I might be doing wrong?

Here is a link to the AMI: https://aws.amazon.com/marketplace/pp/B013FEULQA?qid=1549456410369&sr=0-1&ref_=srh_res_product_title

Usernames tried

ubuntu

ec2-user

centos

admin

root

fedora

wowza

[Karel_Boek]

Hi @Heather Williams, the username is definitely “ec2-user”. If you’re 100% sure that your private key is correct, then you may check if that key is actually the key that is paired with the EC2 instance. In the AWS console, select the EC2 instance, and look for “Key pair name” in the details.

If it still doesn’t work, you could start over again - maybe that’s faster than spending lots of time on try to get this instance to work? By the way, you could also pick any default EC2 instance and install Wowza yourself - see https://www.wowza.com/pricing/installer

[Heather_Williams]

Thanks for the reply. We did verify 100% that we have the SSH key and it was the same one that was paired with the instance and we were using ec2-user and it still wouldn’t let us in.

On a side note I have been trying to duplicate an existing EC2 instance for a client using an AMI and am having issues logging into it as well. I have a theory that Amazon requires the original SSH key that was used when generating the AMI in order to use an AMI even though you technically register a new SSH key when creating an instance with the AMI. I am not sure if it is a security thing but it seems like a huge flaw and I am not sure how you generate an AMI without a default SSH key tied into it so you can use a new one.

I did end up setting up a new instance and manually uploading and installing the linux version of Wowza onto it. Much more work involved than just using your AMI but it works. Really wish we could figure out the AMI issue for future users!

[Andrew_Ramberg]

Hi Heather,

The key used for SSH will be the one selected during the AMI configuration process. On the Launch this Software page, near the bottom you’ll see the Key Pair Settings option. You’ll need to select your Key Pair or create a key pair and then select it from this location.

Then make sure your ssh program is set to use the key pair file for authentication. Username is ec2-user as Karel confirmed.

Best regards,
Andrew