Amahi on AWS - Revision history

Bigfoot65 at 22:42, 14 September 2015

2015-09-14T22:42:09Z

Bigfoot65 at 14:14, 29 March 2015

2015-03-29T14:14:24Z

Bigfoot65 at 16:20, 5 April 2014

2014-04-05T16:20:42Z

Dada216 at 02:30, 17 November 2010

2010-11-17T02:30:12Z

Dada216 at 02:16, 17 November 2010

2010-11-17T02:16:04Z

Dada216 at 01:36, 17 November 2010

2010-11-17T01:36:02Z

Dada216 at 01:33, 17 November 2010

2010-11-17T01:33:40Z

Dada216 at 01:28, 17 November 2010

2010-11-17T01:28:16Z

Cpg: Created page with 'How to run Amahi on Amazon's Cloud Services'

2010-11-16T21:13:00Z

Created page with 'How to run Amahi on Amazon's Cloud Services'

New page

How to run Amahi on Amazon's Cloud Services

← Older revision		Revision as of 22:42, 14 September 2015
Line 1:		Line 1:
−	~~{{MessageBox\|backgroundcolor = #FBB\|~~
−	~~image =Warning.png\|~~
−	~~heading =WARNING\|~~
−	~~message = Fedora 14 is in maintenance mode.<br>[[Amahi 7]] is the latest stable release.}}~~
−	~~----~~
−
−
	{{NeedsUpdate}}		{{NeedsUpdate}}

← Older revision		Revision as of 14:14, 29 March 2015
Line 1:		Line 1:
		+	{{MessageBox\|backgroundcolor = #FBB\|
		+	image =Warning.png\|
		+	heading =WARNING\|
		+	message = Fedora 14 is in maintenance mode.<br>[[Amahi 7]] is the latest stable release.}}
		+	----
		+
		+
	{{NeedsUpdate}}		{{NeedsUpdate}}

← Older revision		Revision as of 16:20, 5 April 2014
Line 1:		Line 1:
		+	{{NeedsUpdate}}
		+
		+
	=Running Amahi on Amazon Cloud computing service.=		=Running Amahi on Amazon Cloud computing service.=
	discussion is ongoing on the amahi forum about this.		discussion is ongoing on the amahi forum about this.

@@ Line 31: / Line 31: @@
 * On the running instance linux system edit file <code>/etc/ssh/sshd_config</code> and uncomment the <code>AllowTcpForwarding yes</code> and <code>GatewayPorts yes</code>
-* On the NATted endpoint check that you have a server listening on LOCAL_PORT, you'll need to have the ssh key that's in the instance <code>~/.ssh/authorized_keys2</code> on this endpoint <code>~/.ssh/id_rsa.pub</code> for this to work this way, if this is not the case you can modify the command adding <code>USERNAME@INSTANCE_PUBLIC_IP</code>
+* On the NATted endpoint check that you have a server listening on LOCAL_PORT, fire up a terminal and do:
 <code>ssh -R INSTANCE_PUBLIC_IP:LOCAL_PORT:localhost:REMOTE_PORT INSTANCE_PUBLIC_IP</code>
 Example:
@@ Line 42: / Line 44: @@
 <code>ssh -R 50.36.23.23:80:localhost:80 50.36.23.23</code>
-and if you point to http://50.36.23.23/ you're actually being replied by the server listening on the NATted IP.
+Now as long as the terminal on the NATted enpoint stays open if you point to http://50.36.23.23/ you're actually being replied by the server listening on the NATted IP.

@@ Line 5: / Line 5: @@
 * Register to Amazon AWS
-* launch instance of AMI "ami-0d638d64"
+* launch instance of AMI "ami-0d638d64", during launch you can setup "security group" during which you have to open ports 80 and 2000 for all Internet IP (0.0.0.0/0)
-* ssh into it with the command shown on the amazon console
+* ssh into it with the command shown on the amazon console, you'll need to save YOUR_KEYPAIR somewhere to do that
 * create a user with:
 <code>useradd -p PASSWORD USERNAME</code>
@@ Line 14: / Line 15: @@
 <code>ssh-keygen</code>
 * upload your ssh key to the running instance with:
-<code>scp -i YOURKEYPAIR.pem ~/.ssh/id_rsa.pub root@INSTANCEPUBLICIP:/home/USERNAME/id_rsa.pub</code>
+<code>scp -i YOUR_KEYPAIR.pem ~/.ssh/id_rsa.pub root@INSTANCE_PUBLIC_IP:/home/USERNAME/id_rsa.pub</code>
 *from your server again move your keypair to the authorized ssh key with:
 <code>mv ~/id_rsa ~/.ssh/authorized_keys2 </code>
 * check that /dev/null is readable, if not do a:
 <code>chmod go+rw /dev/null</code>
-* use <code>route</code> and <code>ifconfig</code> to find out your network setting
+* use <code>route</code> and <code>ifconfig</code> to find out your network setting (if you want a static IP you have to purchase an "elastic IP", please consider that IP persist after reboot but not after stop or termination)
 * create your hda profile accordingly
-as root follow the instruction on the wiki for a [[Self-install]], on reboot disable DHCP and SAMBA server as they conflict with amazon network settings.
+as root follow the instruction for Fedora 12 system on the wiki ([[Self-install]]), on reboot disable DHCP and SAMBA server as they conflict with amazon network settings.

@@ Line 1: / Line 1: @@
-Running Amahi on Amazon Cloud computing service.
+=Running Amahi on Amazon Cloud computing service.=
 discussion is ongoing on the amahi forum about this.
-IMPORTANT: THOSE INSTRUCTIONS DO NOT LEAD TO A FULLY WORKING AMAHI SYSTEM:
+=IMPORTANT: THOSE INSTRUCTIONS DO NOT LEAD TO A FULLY WORKING AMAHI SYSTEM:=
-# Register to Amazon AWS
+* Register to Amazon AWS
-# launch instance of AMI "ami-0d638d64"
+* launch instance of AMI "ami-0d638d64"
-# ssh into it with the command shown on the amazon console
+* ssh into it with the command shown on the amazon console
-# create a user with:
+* create a user with:
 <code>useradd -p PASSWORD USERNAME</code>
-# check that /dev/null is readable, if not do a:
+* check that /dev/null is readable, if not do a:
 <code>chmod go+rw /dev/null</code>
-# from your home computer generate a ssh key if you don't already have one (check ~/.ssh/ for an id_rsa.pub file) with:
+* from your home computer generate a ssh key if you don't already have one (check ~/.ssh/ for an id_rsa.pub file) with:
 <code>ssh-keygen</code>
-# upload your ssh key to the running instance with:
+* upload your ssh key to the running instance with:
 <code>scp -i YOURKEYPAIR.pem ~/.ssh/id_rsa.pub root@INSTANCEPUBLICIP:/home/USERNAME/id_rsa.pub</code>
-#from your server again move your keypair to the authorized ssh key with:
+*from your server again move your keypair to the authorized ssh key with:
 <code>mv ~/id_rsa ~/.ssh/authorized_keys2 </code>
-# check that /dev/null is readable, if not do a:
+* check that /dev/null is readable, if not do a:
 <code>chmod go+rw /dev/null</code>
-# use <code>route</code> and <code>ifconfig</code> to find out your network setting
+* use <code>route</code> and <code>ifconfig</code> to find out your network setting
-# create your hda profile accordingly
+* create your hda profile accordingly
 as root follow the instruction on the wiki for a [[Self-install]], on reboot disable DHCP and SAMBA server as they conflict with amazon network settings.

← Older revision		Revision as of 01:28, 17 November 2010
Line 1:		Line 1:
−	~~How to run~~ Amahi on Amazon'~~s Cloud Services~~	+	Running Amahi on Amazon Cloud computing service.
		+	discussion is ongoing on the amahi forum about this.
		+
		+	IMPORTANT: THOSE INSTRUCTIONS DO NOT LEAD TO A FULLY WORKING AMAHI SYSTEM:
		+
		+	1) Register to Amazon AWS
		+	1) launch instance of AMI "ami-0d638d64"
		+	2) ssh into it with the command shown on the amazon console
		+	3) create a user with useradd -p PASSWORD USERNAME
		+	4) check that /dev/null is readable, if not do a:
		+	chmod go+rw /dev/null
		+	5) from your home computer generate a ssh key if you don't already have one (check ~/.ssh/ for an id_rsa.pub file) with: ssh-keygen
		+	6) upload your ssh key to the running instance with:
		+	scp -i YOURKEYPAIR.pem ~/.ssh/id_rsa.pub root@INSTANCEPUBLICIP:/home/USERNAME/id_rsa.pub
		+	7)from your server again move your keypair to the authorized ssh key with
		+	mv ~/id_rsa ~/.ssh/authorized_keys2
		+	8) check that /dev/null is readable, if not do a:
		+	chmod go+rw /dev/null
		+	9) use route and ifconfig to find out your network setting
		+	10) create your hda profile accordingly
		+
		+	as root follow the instruction on the wiki for a [[Self-install]], on reboot disable DHCP and SAMBA server as they conflict with amazon network settings.