Launching Amazon EC2 Spot Instances with Auto Scaling and Amazon CloudWatch avaliações

console does not work, gives error messages

Michael R. · Revisado há about 9 years

marc c. · Revisado há about 9 years

marc c. · Revisado há about 9 years

Stephen Allen H. · Revisado há about 9 years

Tony S. · Revisado há about 9 years

Francisco M. · Revisado há about 9 years

Alex K. · Revisado há about 9 years

根岸 駿. · Revisado há about 9 years

Roger W. · Revisado há about 9 years

David K. · Revisado há about 9 years

Logan W. · Revisado há about 9 years

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. · Revisado há about 9 years

Mike H. · Revisado há about 9 years

Colin F. · Revisado há about 9 years

José D. · Revisado há about 9 years

Joon K. · Revisado há about 9 years

Alex G. · Revisado há about 9 years

orikasa j. · Revisado há about 9 years

Kathiravan K. · Revisado há about 9 years

Scott P. · Revisado há about 9 years

sabyasachi b. · Revisado há about 9 years

zahi y. · Revisado há about 9 years

John C. · Revisado há about 9 years

Tracy F. · Revisado há about 9 years

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. · Revisado há about 9 years