Creating Amazon EC2 Instances (for Linux) Reviews

Good

anuj t. · Reviewed over 8 years ago

In the last step after assigning the Elastic IP to the EC2 instance, the public DNS changes which drops the previous connection opened in SSH. Just a comment that might be helpful. Used Amazon Linux AMI for the Lab.

Jacobo Noe D. · Reviewed over 8 years ago

Killol M. · Reviewed over 8 years ago

Satisfied

Sivakumar B. · Reviewed over 8 years ago

Xinyu X. · Reviewed over 8 years ago

Omar C. · Reviewed over 8 years ago

Lab was far too basic for the cost given that majority of information was covered in other labs in quest. Of the material the only two 'new' items were covered: Elastic IPs and gathering instance information from 169.254.169.254. The instance information was a copy-paste from the lab and the utility of this meta-data resource for the instance was left to the user to figure out. Elastic IPs were mentioned only to the limit of creating and assigning, with no further explanation nor differentiation from 'public IP' that was already assigned to the instance. On its own this lab should consume fewer credits, and given the lack of additional information when combined with other quest labs the cost should be far lower.

Ed S. · Reviewed over 8 years ago

David T. · Reviewed over 8 years ago

Ryan M. · Reviewed over 8 years ago

Jose Andres P. · Reviewed over 8 years ago

Server still requests "login as", despite specifying key use.

Jeroen K. · Reviewed over 8 years ago

Tyler M. · Reviewed over 8 years ago

Steven G. · Reviewed over 8 years ago

Mohammed R. · Reviewed over 8 years ago

Dharmendra R. · Reviewed over 8 years ago

Jevgenij M. · Reviewed over 8 years ago

Esteban A. · Reviewed over 8 years ago

一般般

weirui f. · Reviewed over 8 years ago

iván m. · Reviewed over 8 years ago

Good

anuj t. · Reviewed over 8 years ago

和人 上. · Reviewed over 8 years ago

ito y. · Reviewed over 8 years ago

Brett C. · Reviewed over 8 years ago

Gregory S. · Reviewed over 8 years ago