First, i don’t have the option to “Open Studio”. Instead, i can only see “Create a SageMaker domain”.
When i click that it endlessly spins and nothing happens. My timer is ticking and my due date is approaching, but i can’t get the lab started.
Please advise.
Hi Aleks. By any chance, are you also logged into a personal AWS account? If so, you may want to log out of that first. Then, retry the lab only with the student credentials automatically set up for you by the Launch App
button in Coursera, and AWS
button in Vocareum. Setting up the lab might take up to 20 minutes because it is a retake. Hope this helps!
I was not logged in another aws account ( i made sure to check that).
It shows me access denied.
Is there a way i can attach a screenshot here?
The errors I get are:
AccessDeniedException
User: arn:aws:sts::957075048904:assumed-role/voclabs/user2663657=Aleksandra_Howell is not authorized to perform: sagemaker:ListDomains on resource: arn:aws:sagemaker:us-east-1:957075048904:domain/* because no VPC endpoint policy allows the sagemaker:ListDomains action
AccessDeniedException
User: arn:aws:sts::957075048904:assumed-role/voclabs/user2663657=Aleksandra_Howell is not authorized to perform: sagemaker:ListModels because no VPC endpoint policy allows the sagemaker:ListModels action
AccessDeniedException
User: arn:aws:sts::957075048904:assumed-role/voclabs/user2663657=Aleksandra_Howell is not authorized to perform: sagemaker:ListEndpoints because no VPC endpoint policy allows the sagemaker:ListEndpoints action
AccessDeniedException
User: arn:aws:sts::957075048904:assumed-role/voclabs/user2663657=Aleksandra_Howell is not authorized to perform: sagemaker:ListNotebookInstances because no VPC endpoint policy allows the sagemaker:ListNotebookInstances action
AccessDeniedException
User: arn:aws:sts::957075048904:assumed-role/voclabs/user2663657=Aleksandra_Howell is not authorized to perform: sagemaker:ListTrainingJobs because no VPC endpoint policy allows the sagemaker:ListTrainingJobs action
Hi Aleks. Yes you can attach a screenshot through the Upload
button when replying.
Please post one showing the Sagemaker Studio screen. That is found after searching for SageMaker
, landing on its homepage, then clicking Studio
on the left sidebar. I think the errors you posted are related to a different command.
Will wait for your update. Thanks!
PROBLEM SOLVED!
It turns out that the issue was caused because i was logging through my employer’s organization (Capital One). I ended up having to create a new personal account ( not through my employer). Unfortunately that meant that i had to register a second time for the training and pay the $49 twice.
Since I will be continuing the training from my personal account and not through my employeer, is it possible to get reimbursed for one of the $49 fees? If i knew that the training would NOT work through my employer, i would have not registered through there.
Thank you!
Interesting. I’m not sure why it didn’t work for your organization’s account. But thanks still for sharing the solution. Will keep this in mind for future learners.
Unfortunately, we don’t make decisions on refunds. Please contact Coursera through email or chat instead and explain the situation to them. I think they’re the ones to handle that.
Thanks again!
same issue with me… pls help @chris.favila @deeplearning
attaching screenshot here
Hi Shweta. Can you check your system clock and sync it to a time server if possible? Here’s one article for reference but feel free to find another resource based on your setup. Then, relaunch the lab from the classroom. Also make sure that you are not logged in to a personal AWS account. You should only be using the student credentials automatically provided during launch. For other lab concerns, please visit this FAQ. Hope these help!
@chris.favila @deeplearning, I have the same issue for lab2. There’s no open studio button. I have checked my system clock and sync it to internet time server.
And I’m not logged into a personal AWS account.
Please help to fix the issue.
Hi Qinghua and welcome to the community! We’ve escalated this to our partners and we’re waiting for a resolution. Kindly monitor this topic for updates. Thanks!