We have created a new Amazon EC2 AMI with ID ami-faea4f93 that can be run for free on EC2 as a “micro” instance. This contains Virtualmin, Webmin, Usermin and all the servers they configure like Apache, Postfix and BIND. The AMI is built on top of Amazon’s own Linux distribution, which is similar to Fedora or CentOS Linux.
Trying to launch another instance of your AMI this morning and I can’t connect…ever! Not even using the EC2 console, it worked fine for me last night…any ideas?
I couldn’t do a BIND DNS server restart. It just fails to start and when I check the log, it says it has some permission problem, although I already sudo the command.
I create a virtual server that create a user for me at virtualmin.
However, I cannot login ftp as that user. Could you tell me how to use ftp for this AMI ?
I install virtualmin at ami-606bb909, and the ftp works fine.
Is there any configuration that I need to do to make the ftp working on this AMI ?
I followed all the steps to setup this instance, converted pem key to ppk, got the public dns to login with WinSCP and cannot login…at any point while setting up the instance I didn’t see a username, i used ec2-user to login as a guess…any idea what I am doing wrong?
I’m planing to migrate one of my virtual-min servers to Amazon.
This is a production server with some important clients.
they have e-mail accounts and websites running.
I’m not sure how to deal with IP changes in Amazon instances.
1 - Is there any specific configuration to guaranty all services like postfix email server, Apache web server, etc will continue to run smoothly on IP change?
If you’ll be running important services on the system, you should get an elastic IP for it. Elastic IPs are assigned and never change, as long as you are subscribed to the IP. You can then assign the IP to your Virtualmin EC2 instance (and if you fire up another EC2 instance to take the place of the old one you can assign the old IP to it).