An update to the EC2 Management Console prevents the Wowza Media Server AMIs from launching properly. The workaround is to specify the default startup package using the
User data field as part of the AMI launch process. To do this:
Configure Instance Details step, open the
Advanced Details section.
User data field, enter the following user data and then select the
As text option.
I checked our current and recently replaced AMI's. The folder
/etc/pki/tls is certainly present, however,
cert.pem is evidently not a default file (I didn't see it). I don't expect this file missing on your end is the result of a Wowza issue.
It is actually the EC2 tools supplied by Amazon that are removing the symlink when the ami is created. It looks like they added a script to the tool that removes all *.pem files when the new image is built.
We have found a workaround and will most likely be raising it as a bug with Amazon but we feel does not warrant a complete rebuild of all AMIs at this stage.
For the current AMIs, the symlink can be reinstated with the following commands.
sudo ln -s certs/ca-bundle.crt cert.pem