Opinie (Maintaining High Availability with Auto Scaling (for Linux))

Seth R. · Sprawdzono ponad 7 lat temu

Istvan R. · Sprawdzono ponad 7 lat temu

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

Christopher C. · Sprawdzono ponad 7 lat temu

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

siddharth s. · Sprawdzono ponad 7 lat temu

Andrew B. · Sprawdzono ponad 7 lat temu

Tola A. · Sprawdzono ponad 7 lat temu

Kevin M. · Sprawdzono ponad 7 lat temu

Enrique V. · Sprawdzono ponad 7 lat temu

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

Jim R. · Sprawdzono ponad 7 lat temu

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

Jason N. · Sprawdzono ponad 7 lat temu

Patrick H. · Sprawdzono ponad 7 lat temu

Brett J. · Sprawdzono ponad 7 lat temu

Excellent

Ron A. · Sprawdzono ponad 7 lat temu

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

Mark T. · Sprawdzono ponad 7 lat temu

Hiroyuki K. · Sprawdzono ponad 7 lat temu

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

Erwan D. · Sprawdzono ponad 7 lat temu

Not refresh correctly the score

Julian P. · Sprawdzono ponad 7 lat temu

Istvan R. · Sprawdzono ponad 7 lat temu

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. · Sprawdzono ponad 7 lat temu

Anitha M. · Sprawdzono ponad 7 lat temu

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

Marc D. · Sprawdzono ponad 7 lat temu

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. · Sprawdzono ponad 7 lat temu

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. · Sprawdzono ponad 7 lat temu

Adrian V. · Sprawdzono ponad 7 lat temu

Danny R. · Sprawdzono ponad 7 lat temu