Updated amazon ec2 (markdown)

Axel Uhl commited 2014-06-25 14:20:33 +0000 commit 7a5e8d5be3c4a90e10941b0e56ec04e10955091d

				wiki/amazon-ec2.md
			
          @@ -267,7 +267,8 @@ Here are the steps to create a load balanced setup:

           - Create a master instance holding all data (see http://wiki.sapsailing.com/wiki/amazon-ec2#Setting-up-Master-and-Replica)

           - Create `n` instances that are configured to connect to the master server

          -- Create a load balancer that redirects everything from port 80 to let's say port 8888.

          +- Create a load balancer that redirects everything from HTTP port 8888 to HTTP port 8888 and leave the other switches and checkboxes on their default value

          +- As "Ping Port" enter HTTP port 8888 and use /index.html as the "Ping Path."

           - Associate all your instances

           - Connect your domain with the IP of the load balancer. It could be a good idea to use an Elastic IP that always stays the same for the domain and associate it with your load balancer. That way you can also easily switch between a load balancer and a single instance setup.

...	...	@@ -267,7 +267,8 @@ Here are the steps to create a load balanced setup:
267	267
268	268	- Create a master instance holding all data (see http://wiki.sapsailing.com/wiki/amazon-ec2#Setting-up-Master-and-Replica)
269	269	- Create `n` instances that are configured to connect to the master server
270		-- Create a load balancer that redirects everything from port 80 to let's say port 8888.
	270	+- Create a load balancer that redirects everything from HTTP port 8888 to HTTP port 8888 and leave the other switches and checkboxes on their default value
	271	+- As "Ping Port" enter HTTP port 8888 and use /index.html as the "Ping Path."
271	272	- Associate all your instances
272	273	- Connect your domain with the IP of the load balancer. It could be a good idea to use an Elastic IP that always stays the same for the domain and associate it with your load balancer. That way you can also easily switch between a load balancer and a single instance setup.
273	274