Changes between Version 82 and Version 83 of InstallationGuidelines/Amazon

Timestamp:

06/21/14 21:03:27 (11 years ago)

Author:

gnarula

Comment:

--

InstallationGuidelines/Amazon

@@ -303 +303 @@
 To troubleshoot any errors in installation of EC2 visit its [http://aws.amazon.com/documentation/ec2/ documentation]. If you encounter problems installing eden on the EC2 instance, you can contact us via [http://webchat.freenode.net/?channels=sahana-eden&uio=d4/ IRC] or the [https://groups.google.com/forum/#!forum/sahana-eden/ mailing list].
 
-== Setting up an EC2 instance as a master node ==
-
-Once you've registered for Amazon's Web Services, login to the EC2 Management Console. You'll be greeted with the EC2 dashboard as in the picture below
+== Installing Deployment Coapp on EC2 ==
+
+* Once you've registered for Amazon's Web Services, login to the [https://console.aws.amazon.com/ec2/v2/home EC2 Management Console]. You'll be greeted with the EC2 dashboard as in the picture below
 
 [[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/InstallationGuidelines/Amazon/Dashboard.png, 75%)]]
 
-Next, click on Launch Instance. This new instance will act as a master node for future deployments. We'll use Debian as the OS since the bootstrapping scripts support it. In the "Select your Amazon Machine Image" pane, select "AWS Marketplace" from the left sidebar. Scroll down, click on "Operating Systems" and select "Debian GNU/Linux"
+* Next, click on Launch Instance. This new instance will act as a master node for future deployments. We'll use Debian as the OS but other distributions may be supported in the future. In the "Select your Amazon Machine Image" pane, select "AWS Marketplace" from the left sidebar. Scroll down, click on "Operating Systems" and select "Debian GNU/Linux"
 
 [[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/InstallationGuidelines/Amazon/SelectAMI.png, 75%)]]
 
-In the next step, select the instance of your choice. The t1.micro instance is a good choice if you're eligible for Free Tier.
-
-Next, in the Configure Instance pane, expand the Advanced Details tab and enter the contents of https://github.com/gnarula/eden_playbook/blob/master/user-data.sh in the User-Data field.
-
-Moving on to Step 6, create a new security group with a rule for SSH and HTTP as shown in the screenshot below.
+* In the next step, select the instance depending on your requirements.
+
+* Next, in the Configure Instance pane, expand the Advanced Details tab and enter the contents of https://github.com/gnarula/eden_playbook/blob/master/user-data.sh in the User-Data field.
+[[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/InstallationGuidelines/Amazon/UserData.png, 75%)]]
+
+* Create a new security group with a rule for SSH and HTTP and Port 8000 as shown in the screenshot below.
 
 [[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/InstallationGuidelines/Amazon/SecurityGroup.png, 75%)]]
 
-Finally, review the configuration and launch the instance. You'll be prompted to select an existing key pair or generate a new one. In case you're a new user or you don't have access to your key, generate a new keypair, save it and proceed.
-
-That's it! Your new instance will have Eden Installed and set up for it to be used as a master node in future deployments. Do note that the deployment takes some time (~10-12 minutes) even after the Web UI states the instance as "Running". Logs for the process may be found by sshing into the newly created instance with your key and viewing /var/log/user-data.log and /var/log/syslog
-
-Note that the script generates a random password for the PostgreSQL database and that is automatically saved in 000_config.py during the setup.
+* Finally, review the configuration and launch the instance. You'll be prompted to select an existing key pair or generate a new one. In case you're a new user or you don't have access to your key, generate a new keypair, save it and proceed.
+
+That's it! The instance will have Deployment Coapp Installed and may be used to install Eden on that instance or any other remote servers. Do note that the installation takes some time (~5 minutes) even after the EC2 Web UI states the instance as "Running". The Coapp may be accessed by browsing to http://instance-public-ip:8000/
+
+Logs for the process may be found by sshing into the newly created instance with your key and viewing /var/log/user-data.log and /var/log/syslog
+
 
 == Next ==