hi,
i don’t need my instance on amazon ec2 running all the time, and i don’t need to terminate it because i configured many settings that fit my needs.so i need to stop it so as not to be charged all the time, but i found the stop option is grayed-out
please need a help
thanks
Ram
Ram,
The only good option is to configure a startup package. Then you can terminate the instance when you don’t need it and start one up that is automatically configured as you want it. It’s mostly identical set of files to the your configuration, whatever is different, application and conf folders and Application.xml. If you have made changes to other configuration files, e.g. Server.xml, you will include that in the startup package.
Take a look at the Wowza EC2 guide for details on creating a startup package:
https://www.wowza.com/resources/WowzaMediaServerForEC2_UsersGuide.pdf
Richard
In ElasticFox there is a button labeled “Open Binary File” in the launch instance dialog. That’s how to include startup zip file with ElasticFox.
Richard
Ram,
You save the startup package locally, and included it when you launch an instance by clicking on that button in Elastic Fox.
Yes, you can apply a patch using a startup package. It if puts the files size over the limit (16KB I think) you have to use download tag in the startup.xml file:
<Download>
<URL>http://[web-server]/jarfiles.zip</URL>
<Destination>/usr/local/WowzaMediaServer/lib/jarfiles.zip</Destination>
<Action>UNZIP</Action>
</Download>
If you replace the /conf/Server.xml file using a startup package, there are two EC2 specific ServerListeners that you should be sure to include.
Richard
Startup packages are your friend.
It’s a little tricky to do a startup package via the AWS web console, however. Best way to launch an AMI with a startup package is via the java AMI tools.
thanks guys,
i’m in a need for more details about writing the startup.xml file and where to save it permanently,
another point, i need to Apply patch 5 to that server? can i do that as startup package??
Ram