Maintaining High Availability with Auto Scaling (for Linux) Reviews

Archit M. · Reviewed almost 7 years ago

Steve L. · Reviewed almost 7 years ago

Edward W. · Reviewed almost 7 years ago

satheya k. · Reviewed almost 7 years ago

Unable to connect any instances.... public ip not reachable

balakrishnan p. · Reviewed almost 7 years ago

Przemo D. · Reviewed almost 7 years ago

Rudy K. · Reviewed almost 7 years ago

It was a little difficult but I was able to complete

Z. Jared B. · Reviewed almost 7 years ago

Muralidhar M. · Reviewed almost 7 years ago

Long D. · Reviewed almost 7 years ago

Muralidhar M. · Reviewed almost 7 years ago

手順28のインスタンスタイプはt1ではなくt2が正しい。 手順88、102はメトリクス選択の前に”グラフ化したメトリクス”タブでしか変更できない。

Michel T. · Reviewed almost 7 years ago

Samuel S. · Reviewed almost 7 years ago

Hiroya A. · Reviewed almost 7 years ago

Frank F. · Reviewed almost 7 years ago

Art S. · Reviewed almost 7 years ago

Jack H. · Reviewed almost 7 years ago

David V. · Reviewed almost 7 years ago

Estanislao B. · Reviewed almost 7 years ago

Muralidhar M. · Reviewed almost 7 years ago

Bartlomiej S. · Reviewed almost 7 years ago

autoscaling -1 not shwon

James Y. · Reviewed almost 7 years ago

Jim K. · Reviewed almost 7 years ago

In the Putty connection instructions, there is no instructions to login as ec2-user or to set timeout to 30, causes problems. Also once a second instance is auto initiated, the cpu load on the first instance dropped to 0 and then autoscaling subsequently dropped it back down to 1 instance.

Mark A. · Reviewed almost 7 years ago

Awkward start but got good Got a bit confused with the instructions running into linux approach. Didn't spot I had alreay done it with putty

Nick M. · Reviewed almost 7 years ago