Maintaining High Availability with Auto Scaling (for Linux) Reviews

Andreas A. · Reviewed over 8 years ago

good lab

Mallikharjuna J. · Reviewed over 8 years ago

日本語版テキスト(4.0.1)が古すぎてエラーが発生する。英語版テキスト(4.2)では問題ない。

赤平 勝. · Reviewed over 8 years ago

Kirti S. · Reviewed over 8 years ago

Kirti S. · Reviewed over 8 years ago

ran out of time. Need more time.

Srinivas K. · Reviewed over 8 years ago

Donald E. · Reviewed over 8 years ago

Lingaraj N. · Reviewed over 8 years ago

Wes O. · Reviewed over 8 years ago

Rik S. · Reviewed over 8 years ago

Starting on step 49, the instructions are missing to direct students to open new PuTTy session into a newly created instance since the previous instance was terminated.

Oleg K. · Reviewed over 8 years ago

George P. · Reviewed over 8 years ago

Adam K. · Reviewed over 8 years ago

Donald L. · Reviewed over 8 years ago

Ken L. · Reviewed over 8 years ago

I liked it

Derald M. · Reviewed over 8 years ago

Tommy T. · Reviewed over 8 years ago

Josh B. · Reviewed over 8 years ago

It was frustrating to get the autoscaling policies work. There were some fields in CloudWatch screens that were insufficiently documented. CPU utilization is not a very real world thing on which to trigger autoscaling. We should have used a canary (a lambda) to trigger autoscaling when response time becomes unmanageable. You need a real web application to test.

Eric G. · Reviewed over 8 years ago

thor h. · Reviewed over 8 years ago

Ryan H. · Reviewed over 8 years ago

Chris S. · Reviewed over 8 years ago

asdf

John D. · Reviewed over 8 years ago

Marcin K. · Reviewed over 8 years ago

Bryon B. · Reviewed over 8 years ago