Opinie (Introduction to Amazon EC2)

Antonio R. · Sprawdzono około 7 lat temu

Satisfied, but problems to acces the lab at the beginning.

Raúl C. · Sprawdzono około 7 lat temu

Héctor R. · Sprawdzono około 7 lat temu

Satisfied, but problems to acces the lab at the beginning.

Raúl C. · Sprawdzono około 7 lat temu

bad conecction

Jose C. · Sprawdzono około 7 lat temu

Roberto O. · Sprawdzono około 7 lat temu

Darrin N. · Sprawdzono około 7 lat temu

Casey G. · Sprawdzono około 7 lat temu

Srecko V. · Sprawdzono około 7 lat temu

very satisfied

Joshua F. · Sprawdzono około 7 lat temu

Ola F. · Sprawdzono około 7 lat temu

4 stars. The httpd server did not load (verified by inspecting the log). I restarted the image several times and even tried adding "logger" lines. After the first start, when I clicked on view log I got a black screen.

Wade H. · Sprawdzono około 7 lat temu

Colin M. · Sprawdzono około 7 lat temu

Mun Kit T. · Sprawdzono około 7 lat temu

Was good for practicing.

Lewis R. · Sprawdzono około 7 lat temu

Denis D. · Sprawdzono około 7 lat temu

Yes

Bilkiss A. · Sprawdzono około 7 lat temu

good

RAMU M. · Sprawdzono około 7 lat temu

Yuh K. · Sprawdzono około 7 lat temu

Michael M. · Sprawdzono około 7 lat temu

An FYI - There may be an issue when kicking off the labs instance with the user provided bash script. When reviewing the step 26 - Get System Log I could not validate validate the http package was installed from the user data. I was able to properly set up the Security Group to access the web server, but the test page was not being served at all. I suspected that there was an issue with the provided User Data script during the instance launch, To validate, I re-enable SSH and manually ran the commands to install the http package and found that there was a permission issue when trying to create the index.html file in the /var/www/html/ directory. I navigated to the /var/www/html/ directory and manually created the index.html file using 'sudo nano index.html' and dropping the html code in it. After restarting the httpd service the page rendered as expected in my browser. Thanks

Scott J. · Sprawdzono około 7 lat temu

ok

Danna F. · Sprawdzono około 7 lat temu

Everything worked except the web server never worked. It gave connection refused, as if the http server never got installed. So, I launched another instance in the exact same way, but this time enabled an SSH key and added SSH 22 to the security group so I could ssh in and see what the problem was. It was stuck here, just hanging indefinitely: root 3252 0.1 3.0 147208 30964 ? Ss 04:11 0:00 /usr/bin/python /usr/bin/cloud-init modules --mode=final root 3259 0.0 0.0 4284 788 ? S 04:11 0:00 \_ tee -a /var/log/cloud-init-output.log root 3260 0.0 0.2 13708 2736 ? S 04:11 0:00 \_ /bin/bash /var/lib/cloud/instance/scripts/part-001 root 3261 1.3 6.9 298612 70220 ? S 04:11 0:03 \_ /usr/bin/python /usr/bin/yum -y update root 3272 0.0 0.2 13708 2684 ? S 04:11 0:00 \_ /bin/sh /var/tmp/rpm-tmp.IX694k 1 root 3291 0.0 0.1 31172 1468 ? S 04:11 0:00 \_ systemctl try-restart update-motd.service Anyhow, you should look into this. Somehow the "yum -y update" is causing the system to hang forever. I would recommend removing the "yum -y update" command from the user-data script you supply, so it doesn't get stuck here.

David K. · Sprawdzono około 7 lat temu

good

Zoltan S. · Sprawdzono około 7 lat temu

Luca B. · Sprawdzono około 7 lat temu