Introduction to Amazon Relational Database Service (RDS) - SQL ServerIr al Laboratorio
I was unable to connect to EC2 instance, presumably because of firewall rules on my side. Watching someone ruin through it yesterday was very nice.
It took 3 attempt for me to complete this lab. First attempt, I couldn't copy and paste scripts from step 33 to RDP server. Second Attempt, I couldn't RDP to the server pre-created because I can't authenticate with supplied password from lab. My third attempt was success, everything went well. I'm not sure if it was me or Qwiklabs causing the complications from my first two attempts. Anyways...I'm giving this 5 stars since it all worked out for me in the end.
Timing is not enough. System was too slow. Two hours required for this lab. Instructions has to be updated in couple places. i.e., for selecting two instnaces
Quick and good instructions.
It seemed good. I had problems connecting from work so I was slowed by a bad wifi connection. No fault of the lab of course.
Steps are very clear and easy understandle. Hands on lab is very useful
Not very... Time limits don't match what is required, perhaps only for me, to complete the project.
Very good tutorial!
I was stuck on step 33 of the lab. I couldn't copy script to create database on my RDP session and the lab time passed until I had only 1 minute left so I ended the lab session. I opened ticket with support. I will try and start a new session in an effort to complete this lab.
EC2 ports were not opened.
The first time I tried the lab I never got a public IP or public DNS so I emailed support. After the lab timed out (50 minutes), I tried launching the lab again and it worked correctly. The second time I did the lab it was very informative. Thank you.
Nice walkthrough.Material helped alot
I have emailed support because the lab did not work at all for me. I never got a public IP or public DNS for my EC2 instance so I was never able to actually start the lab. Hopefully, someone gets it fixed and resets my lab so I can actually complete it. Thank you. Kyle Poling