I installed Learning Locker using Community AMI on AWS and the system said that it successfully build and running and I can connect to my server using ssh, but when I access public DNS of my instance I always get error 404 not found, and my server running nginx, ubuntu 10.4
I do not have a technical support while I use a free AWS account
So, what should I do?
Related
I'm facing some trouble while trying to start a windows service that I've created with Apache Daemon on an Amazon EC2 Instance (Windows Server 2012 R2). The error I'm getting is "Windows could not start the service_name on local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1."
I checked some other links and most of the similar problems are related to Apache servers issues, but I already have Apache Tomcat working perfectly here and the problem seems to be related to the windows service only.
Does anyone have any idea?
I have Apache server running on Centos5.4 Ec2 instance. Unfortunately while removing Bash from Centos, it also removed basic shared libraries.
Now afterward I can't SSH to that EC2 instance but Apache server is still running (I can access my site through URL).
Any idea how can I get the SSH access back? or can repair Centos Ec2 instance?
Thanks!
You can always contact the AWS support directly. They are very accommodating. send a message to them and they will recover your access, if it is doable from their end.
You may call, or you may send a message from your AWS account.
I need to setup a web server and a database server on EC2.
It should be easy to migrate to another service provider later.
Currently, I have a web server and a database server, each running on separate EC2 micro instances with software installed there remotely.
Can we run a vagrant box on these micro instances with pre-installed and pre-configured softwares like LAMP stack and use that instead. So I will end with 2 vagrant boxes , one for web server another for database server.
Amazon provides already means to copy an instance but it is copied to another EC2 instance only probably .. If there is need to move to some other provider, it will be same process of re-installing all. So, an own virtual box installed on Amazon's virtual box is what i was looking into..
I don't know how good or bad it is.. I doubt if this will affect performance as well. Please share your views. Target is to have env prepared locally and have flexibility to deploy it on any service provider easily.
Running vagrant inside your AWS box is probably not the right solution. Have you looked into the Vagrant AWS provider?
That will allow you to setup and provision your AWS boxes with Vagrant and Puppet or Chef... if you are using Puppet or Chef to provision your servers then you will have a very portable "scripted" install for your servers that can easily be moved to another provider at a later date...
So running a virtual machine, on another virtual machine probably isn't the best. But if you want to install Vagrant on Amazon Linux you can do:
wget https://releases.hashicorp.com/vagrant/2.2.4/vagrant_2.2.4_x86_64.rpm
sudo rpm -ivh vagrant_2.2.4_x86_64.rpm
The RPM is the Centos version from the downloads page here: https://www.vagrantup.com/downloads.html
But then you cannot install virtualbox to run a VM. So it doesn't actually work anyways.
i am complete noob when comes to Linux . how can i connect remotely desktop or Gui to a a Ubuntu Server Cloud Guest 11.10 (Oneiric Ocelot) server in amazon aws from a windows 7 machine ,
can some one give me a link to complete tutorial
I'm going to go ahead and assume your remote Ubuntu instance doesn't have an X server installed -- i.e. you're using the command line version.
Download and install Putty and you should be able to connect to your AWS instance using the SSH keys you initially set up.
Also, recently AWS has added a new feature,
You can now log in to an EC2 instance from the AWS Management Console using an integrated SSH client.
Just right on the ec2 instance from the aws management console and click on connect and
select the second option - Connect from your browser using the MindTerm SSH Client (Java Required).
Specify the private key path and click on "launch mindterm".. thats it.
I created an instance of ubuntu ec2 yesterday and I was trying to configure it and I stopped the serer before going home last night, when I tried log on to the same instance using ssh from my ubuntu I am getting an error which says connection timed out. I am not able to login to the instance now
If you stopped the instance, and the instance was ebs-backed then you should be able to start it using the ec2 api.
Describe the instance using the ec2-describe-instances/instance-attributes api and use ec2-run-instance start it. Once started, use the above api to retrieve the public dns name.
Using this you should be able to login to that same machine again.
if you have terminated an instance-store based virtual machine, then you can kiss it goodbye.