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

Andreas A. · Revisado há over 8 years

good lab

Mallikharjuna J. · Revisado há over 8 years

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

赤平 勝. · Revisado há over 8 years

Kirti S. · Revisado há over 8 years

Kirti S. · Revisado há over 8 years

ran out of time. Need more time.

Srinivas K. · Revisado há over 8 years

Donald E. · Revisado há over 8 years

Lingaraj N. · Revisado há over 8 years

Wes O. · Revisado há over 8 years

Rik S. · Revisado há over 8 years

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

George P. · Revisado há over 8 years

Adam K. · Revisado há over 8 years

Donald L. · Revisado há over 8 years

Ken L. · Revisado há over 8 years

I liked it

Derald M. · Revisado há over 8 years

Tommy T. · Revisado há over 8 years

Josh B. · Revisado há over 8 years

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

thor h. · Revisado há over 8 years

Ryan H. · Revisado há over 8 years

Chris S. · Revisado há over 8 years

asdf

John D. · Revisado há over 8 years

Marcin K. · Revisado há over 8 years

Bryon B. · Revisado há over 8 years