b1d5dc7e412e675d6e050fe0c5ec936b7c0b2f29
wiki/amazon-ec2.md
| ... | ... | @@ -137,9 +137,14 @@ Here are the steps to create a load balanced setup: |
| 137 | 137 | |
| 138 | 138 | - Create a master instance holding all data |
| 139 | 139 | - Create `n` instances that are configured to connect to the master server |
| 140 | -- Create a load balancer |
|
| 140 | +- Create a load balancer that redirects everything from port 80 to let's say port 8888. |
|
| 141 | 141 | - Associate all your instances |
| 142 | -- Connect your domain with the IP of the load balancer |
|
| 142 | +- 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. |
|
| 143 | + |
|
| 144 | +Two things are still needed before this setup can be executed: |
|
| 145 | + |
|
| 146 | +- Make it possible to configure instances that way that they automatically connect to a master upon start |
|
| 147 | +- Check what happens if the ELB acts as a transparent proxy not revealing the underlying instance name and address (should be) |
|
| 143 | 148 | |
| 144 | 149 | ### Access MongoDB database |
| 145 | 150 |