Maintaining High Availability with Auto Scaling (for Linux) avaliações

Archit M. · Revisado há almost 7 years

Steve L. · Revisado há almost 7 years

Edward W. · Revisado há almost 7 years

satheya k. · Revisado há almost 7 years

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

balakrishnan p. · Revisado há almost 7 years

Przemo D. · Revisado há almost 7 years

Rudy K. · Revisado há almost 7 years

It was a little difficult but I was able to complete

Z. Jared B. · Revisado há almost 7 years

Muralidhar M. · Revisado há almost 7 years

Long D. · Revisado há almost 7 years

Muralidhar M. · Revisado há almost 7 years

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

Michel T. · Revisado há almost 7 years

Samuel S. · Revisado há almost 7 years

Hiroya A. · Revisado há almost 7 years

Frank F. · Revisado há almost 7 years

Art S. · Revisado há almost 7 years

Jack H. · Revisado há almost 7 years

David V. · Revisado há almost 7 years

Estanislao B. · Revisado há almost 7 years

Muralidhar M. · Revisado há almost 7 years

Bartlomiej S. · Revisado há almost 7 years

autoscaling -1 not shwon

James Y. · Revisado há almost 7 years

Jim K. · Revisado há almost 7 years

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. · Revisado há almost 7 years

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. · Revisado há almost 7 years