Maintaining High Availability with Auto Scaling (for Linux) recensioni

Seth R. · Recensione inserita oltre 7 anni fa

Istvan R. · Recensione inserita oltre 7 anni fa

The instance without a name does not appear to be present.

Christopher C. · Recensione inserita oltre 7 anni fa

i completed everything ,my score remained on 15/20 even though i was able to view auto scaling

siddharth s. · Recensione inserita oltre 7 anni fa

Andrew B. · Recensione inserita oltre 7 anni fa

Tola A. · Recensione inserita oltre 7 anni fa

Kevin M. · Recensione inserita oltre 7 anni fa

Enrique V. · Recensione inserita oltre 7 anni fa

Good intro to the CLI and using to create launch configuration and AutoScaling group

Jim R. · Recensione inserita oltre 7 anni fa

the sns portion doesn't seem correct and the scoring system wasn't updating for me

Jason N. · Recensione inserita oltre 7 anni fa

Patrick H. · Recensione inserita oltre 7 anni fa

Brett J. · Recensione inserita oltre 7 anni fa

Excellent

Ron A. · Recensione inserita oltre 7 anni fa

couldn't get verify autoscaling and create autoscaling notification or using cloudwatch to monitor autoscaling objectives to complete!

Mark T. · Recensione inserita oltre 7 anni fa

Hiroyuki K. · Recensione inserita oltre 7 anni fa

Using CloudWatch to monitor autoscaling score point were never granted even though the exercise was successful (scaling up and down with notification)

Erwan D. · Recensione inserita oltre 7 anni fa

Not refresh correctly the score

Julian P. · Recensione inserita oltre 7 anni fa

Istvan R. · Recensione inserita oltre 7 anni fa

In the autoscaling actions (step #86), my instance of the lab showed two options in the drop-down box, both named lab-as-group.

Garrick D. · Recensione inserita oltre 7 anni fa

Anitha M. · Recensione inserita oltre 7 anni fa

I had issues with the region versus availability zone, which was not explained very well.

Marc D. · Recensione inserita oltre 7 anni fa

Lab works now and previous error reported was user error as region (us-west-2) instead of availability zone (us-west-2a) needed to be specified in the script in #26. Thanks to support for pointing this out.

Christopher O. · Recensione inserita oltre 7 anni fa

It appears the monitoring for the scoring is based off the instance name generated at startup. I accidently restarted the AWS command line instance and the public DNS changed (so I had to redo my SSH conection script, no problem) but making it so that scoring no longer worked. Something

Cori E. · Recensione inserita oltre 7 anni fa

Adrian V. · Recensione inserita oltre 7 anni fa

Danny R. · Recensione inserita oltre 7 anni fa