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

console does not work, gives error messages

Michael R. · Reviewed около 9 лет ago

marc c. · Reviewed около 9 лет ago

marc c. · Reviewed около 9 лет ago

Stephen Allen H. · Reviewed около 9 лет ago

Tony S. · Reviewed около 9 лет ago

Francisco M. · Reviewed около 9 лет ago

Alex K. · Reviewed около 9 лет ago

根岸 駿. · Reviewed около 9 лет ago

Roger W. · Reviewed около 9 лет ago

David K. · Reviewed около 9 лет ago

Logan W. · Reviewed около 9 лет 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 около 9 лет ago

Mike H. · Reviewed около 9 лет ago

Colin F. · Reviewed около 9 лет ago

José D. · Reviewed около 9 лет ago

Joon K. · Reviewed около 9 лет ago

Alex G. · Reviewed около 9 лет ago

orikasa j. · Reviewed около 9 лет ago

Kathiravan K. · Reviewed около 9 лет ago

Scott P. · Reviewed около 9 лет ago

sabyasachi b. · Reviewed около 9 лет ago

zahi y. · Reviewed около 9 лет ago

John C. · Reviewed около 9 лет ago

Tracy F. · Reviewed около 9 лет 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 около 9 лет ago