After a routine reboot of a Linux ec2 instance with 1 small root volume and 1 small attached volume I was not able to ssh into the instance. It is not clear why rebooting the instance caused it to be inaccessible from ssh. The instance showed as running in the AWS console but ssh, http,etc was not responsive. I tried to create an AMI from this running instance.
I'm about to start using AWS for the first time.
From what I understood, when you terminate an instance or start a new one, all the data is lost. For user data I understand you are supposed to use cloud storage such as S3. That's ok.
Now what about all the configurations? Say I spend 2 hours setting up all the apache and PHP configuration or whatnot.
I'm just setting up my AWS server & I'm trying to use the EC2 Console to terminate some extra instances that I generated via the AWS for Eclipse toolkit's New Project >> AWS Java Web Project utility. Unfortunately, every time I stop, then terminate such an instance via the EC2 Console, it automatically recreates & reactivates itself!
I currently have one EC2 instance that is starting to send alerts for high CPU usage. I want to create another instance and use this instance for the database and keep my existing instance for the web server.
I have been looking for hours, for a way to set up an OpenVPN server on an Amazon EC2 instance that's running Windows Server 2008 R2.
All of the tutorials I have found deal with EC2 Linux, Ubuntu, etc. And we have already bought a Windows Reserved instance, so switching is not an option.
I have tried translating the commands, but since I am not well versed in Linux, this has been a challenge.
I am using Elasticfox and when I click on the stop a EBS backed instance, it will terminate it immediately, instead of ONLY STOPPING the instance. How do I fix this? I want to be able to restart the instance after I stopped it.
Ok. So this is my plan. I'll have a micro instance run a batch file to start the server at 6AM and stop the server at 10PM. The micro instance will be on all the time so I could leverage the webserver on that machine.
I'm migrating my development environment to the cloud to help with working remotely, and I've just come up against a bit of a roadblock.
I have an Amazon EC2 instance running Windows 2008 R2, and I can configure the environment there to my needs.
I was contracted to make a groupon-clone website for my client. It was done in PHP with MYSQL and I plan to host it on an Amazon EC2 server. My client warned me that he will be email blasting to about 10k customers so my site needs to be able to handle that surge of clicks from those emails. I have two questions:
1) Which Amazon server instance should I choose?