Launching Amazon EC2 Spot Instances with Auto Scaling and Amazon CloudWatch Reviews

console does not work, gives error messages

Michael R. · Reviewed about 9 years ago

marc c. · Reviewed about 9 years ago

marc c. · Reviewed about 9 years ago

Stephen Allen H. · Reviewed about 9 years ago

Tony S. · Reviewed about 9 years ago

Francisco M. · Reviewed about 9 years ago

Alex K. · Reviewed about 9 years ago

根岸 駿. · Reviewed about 9 years ago

Roger W. · Reviewed about 9 years ago

David K. · Reviewed about 9 years ago

Logan W. · Reviewed about 9 years ago

failed to launch last week. got through the lab today. It was mostly copy/paste and most of the time was spent waiting for things to happen. it would have been better to use the console to create the autoscaling, spot instances, and alarms.

Peter K. · Reviewed about 9 years ago

Mike H. · Reviewed about 9 years ago

Colin F. · Reviewed about 9 years ago

José D. · Reviewed about 9 years ago

Joon K. · Reviewed about 9 years ago

Alex G. · Reviewed about 9 years ago

orikasa j. · Reviewed about 9 years ago

Kathiravan K. · Reviewed about 9 years ago

Scott P. · Reviewed about 9 years ago

sabyasachi b. · Reviewed about 9 years ago

zahi y. · Reviewed about 9 years ago

John C. · Reviewed about 9 years ago

Tracy F. · Reviewed about 9 years ago

This lab is confusing and needs clarification in its instructions. It sounds as if you want the user to locate an AMI id and replace that new ID with the ami-1b3b462b ID listed in the example but the account at this point has no custom AMIs associated with it so the user is not sure if there was supposed to be an AMI that was not created for the lab session or if they are supposed to go into the public AMIs and just randomly select an AMI-id. Also aws ec2 describe-images fails when logged into the bastion as the ec2-user and you instruct the user to run that to get an AMI-id!!!!!

Cameron S. · Reviewed about 9 years ago