wiki/amazon-ec2.md
... ...
@@ -275,23 +275,23 @@ Here are the steps to create a load balanced setup:
275 275
276 276
It is important to understand that it wouldn't help to let all traffic run through our central Apache httpd server which usually acts as a reverse proxy with comprehensive URL rewriting rules and macros. This would make the Apache server the bandwidth bottleneck. Instead, the event traffic needs to go straight to the ELB which requires the event DNS domain name to be mapped to the ELB's host name. You need to set this up in the "Route 53" DNS server which you find in the Amazon Services drop-down.
277 277
278
-<img src="/wiki/images/amazon/Route53_1.png" width="100%" height="100%"/>
278
+<img src="/wiki/images/amazon/Route53_1.png" />
279 279
280 280
Go to the "Hosted Zones" entry
281 281
282
-<img src="/wiki/images/amazon/Route53_2.png" width="100%" height="100%"/>
282
+<img src="/wiki/images/amazon/Route53_2.png" />
283 283
284 284
and select the `sapsailing.com.` row,
285 285
286
-<img src="/wiki/images/amazon/Route53_3.png" width="100%" height="100%"/>
286
+<img src="/wiki/images/amazon/Route53_3.png" />
287 287
288 288
then click on "Go to Record Sets." You will then see the record sets for the `sapsailing.com.` domain:
289 289
290
-<img src="/wiki/images/amazon/Route53_4.png" width="100%" height="100%"/>
290
+<img src="/wiki/images/amazon/Route53_4.png" />
291 291
292 292
Click on "Create Record Set" and fill in the subdomain name (`myspecificevent` in the example shown below) and as the value use the host name (A-record) of the ELB that you find in the ELB configuration.
293 293
294
-<img src="/wiki/images/amazon/Route53_5.png" width="100%" height="100%"/>
294
+<img src="/wiki/images/amazon/Route53_5.png" />
295 295
296 296
Amazon ELB is designed to handle unlimited concurrent requests per second with “gradually increasing” load pattern (although it's initial capacity is described to reach 20k requests/secs). It is not designed to handle heavy sudden spike of load or flash traffic because of its internal structure where it needs to fire up more instances when load increases. ELB's can be pre-warmed though by writing to the AWS Support Team.
297 297