I was able to launch the AWS console about an hour ago and opened the notebook to run the pip installs. However, the notebook got disconnected in 15 mins; I reloaded the page and now I’m not able to launch the AWS console.
When I click the “Start Lab” button, it shows a message:
AWS account deactivated at 2023-08-13T17:24:28-07:00
Same error, but caused by different issue. I selected the wrong instance when first launching kernel, then I tried to change it, it failed to launch 4 times. I shut down the console and went back to ‘Start Lab’, now I just get the ‘Account Deactivated…’ message and can’t launch AWS console.
I’m having the same problem. I was about 20 mins into the first lab and the kernel suddenly disconnected and when I tried to re-start the notebook kernel I got the dreaded “Deactivated from AWS…” message. This REALLY, REALLY makes me NEVER want to use AWS going forward…
I guess I’ll wait a bit and try again…
Hi Adam. Please make sure that you’re selecting the right instance type exactly as shown in the screenshot in the notebook. That is usually ml.m5.2xlarge but please double check. That is usually the problem when the kernel crashes. Hope this helps.
Hi @chris.favila , Yes, I double checked this when running the Kernal. But I closed the AWS instance to try refresh it and cannot get start AWS from the first Vocareum Labs page.
@esanina I am facing the same issue. As the kernel got inactive, I closed the console. Now when I try opening the console, it’s giving me account deactivation error. It’s already been an hour since I started the lab.
The AWS on top left corner on Vocareum Labs page shows Green, but nothing is happening on click (it’s not taking me to the AWS console)
Did your issue get resolved automatically after waiting for sometime?
What-if the issue is not resolved within 50mins of the remaining labs time?
Will you get a chance to complete the assignment later?
Hi Monica. You should be able to access the lab now. On your next attempt, please make sure that you use the same instance type shown on the screenshot in the notebook. That is most likely ml.m5.2xlarge but please double check. You might have to scroll down to the “All Instances” section to see it. If you use any other instance type, the kernel might crash, or your account might get deactivated.
Also, starting the lab might take up to 20 minutes because this is a retake.
Hi everyone! Closing this topic because there is a known solution. If you get a notification saying your AWS is deactivated, please fill out this form and we will work to re-enable your access.
On your next attempt, please make sure that you use the same instance type shown on the screenshot in the notebook. That is most likely ml.m5.2xlarge but please double check. You might have to scroll down to the “All Instances” section to see it. If you use any other instance type, the kernel might crash, or your account might get deactivated.
If you encounter other issues, please create (or search for) a topic here in our community. Our mentors would be glad to assist. Thank you!