Practice Lab 1: Comparing the Query Performance Between Row-Oriented and Column-Oriented Databases
aws console url is not working please help me with this issue
Hi,
Please request a lab refresh to continue.
I have the same problem. When I ask to refresh the lab, the instructions say to copy and paste this command: cat /home/coder/vocapi_logger > vocapi_logger the coursera terminal doesn’t recognize it can someone help ?
Hi,
Have you tried typing the cat /home/coder/vocapi_logger > vocapi_logger in the lab terminal?
If yes, could you please do a screenshot of the error? Thanks!
main problems is because .aws/aws_console_url file is empty
solved the program thanks
hello, for the past 3 weeks i have not been able to do any work. My terminal crashed on my programming assignment, i had the lab reset 3 times and still not results. my C3W3 Practice Lab 1 once again does not generate any link for AWS console. The conditions are unworkable and discouraging at this point… no matter how many times I fill a reset form, nothing works… I had 76/100 on my Programming assignment on C3W2 because of this. Please someone review my work and grade it so i can pass it, because by now i have spend an entire month of subscription doing nothing, because im not able to… Your help is very much appreciated.
Hi @aandonov, sorry for the inconvenience.
Tagging one of our course staff for support — hi @hawraa.salami, we’ve got another case where the AWS console link isn’t working, and multiple lab refreshes haven’t resolved it. Could you please take a look when you get a chance? Thanks so much!
Same issue here: the .aws/aws_console_url file is empty and doesn’t get populated after a reboot or after waiting for the lab to time out.
I tried following the console link from the vocapi_logger output, but it said the session has expired (it hadn’t been 15 minutes since the lab had loaded). Maybe I haven’t logged out of the console after the previous lab, but I didn’t get any notifications within the lab environment.
After logging out from the console and restarting the lab, the vocapi_logger contains no link and the .aws/credentials values are all empty.
Calling vocapi_call_get_aws_console_url.sh directly runs into permission issues.
Below is my log:
vocapi logger
Run count initialized to 0
.aws directory and aws_console_url file are created
Running the vocapi_call at Thu Jul 3 06:51:27 PM UTC 2025
Using LAB_SPACE_ID: sicynpxsnant
START_LAB_DATA received: {'lab_data': {'partid': '****636', 'assignmentid': '****635', 'courseid': '62825'}}
Unsuccessful vocapi call to start lab
Error: Failed operation: Start. Lab is in state: CREATE_FAILED, please end lab and wait for it to complete.
Initial Lab state: Starting
Lab is still starting. Checking again in 30 seconds...
Lab state after check: Failed
Final Lab state after loop: Failed
AWS Console URL extracted:
AWS credentials file created at /home/coder/.aws/credentials
AWS config file created at /home/coder/.aws/config
Running the vocapi_call_get_aws_console_url at Thu Jul 3 06:52:06 PM UTC 2025
Current run count: 0
Using LAB_SPACE_ID: sicynpxsnant
START_LAB_DATA received: {'lab_data': {'partid': '****636', 'assignmentid': '****635', 'courseid': '62825'}}
--------------------------
--------------------------
vocapi response status: success
Extracted AWS Console URL
AWS Console URL written to /home/coder/.aws/aws_console_url
Run count incremented to: 1
Run count written to /home/coder/vocapi_call_run_count
Starting the 2-hour wait at Thu Jul 3 06:52:09 PM UTC 2025
Starting the vocapi_call_wrapper at Thu Jul 3 06:52:09 PM UTC 2025
Iteration 1 of 8 started at Thu Jul 3 06:52:09 PM UTC 2025
Sleeping for 900 seconds before next iteration...
@arsegorov @aandonov @Amar_Shilvanth Thank you all for your patience, there was a problem with loading the data to the redshift cluster because of the recent dc2 deprecation. The lab template is now fixed and you should have access to the lab (practice lab 1 of C3W3).
Thank you @benjamintabaresjr
1 Like
C3W3Lab1 and C3W2 assignments are not related.
We fixed the template issue in C3W3Lab 1
Thanks! It works for me now.
@hawraa.salami C3W3 Practice Lab 2 seems to be having the same issue.
@arsegorov Oh, thank you for letting me know! I will check the lab within one hour and so, and I’ll get back to you.
@arsegorov I was able to run the lab, could you please share your lab id so I can check your AWS account? And could you please explain the problem you encountered? (empty link to AWS console)?
@hawraa.salami My lab id is fydtitwdhzvo, and yes, the AWS URL is missing.
More details here:
vocapi logger
Run count initialized to 0
.aws directory and aws_console_url file are created
Running the vocapi_call at Thu Jul 10 10:09:44 PM UTC 2025
Using LAB_SPACE_ID: fydtitwdhzvo
START_LAB_DATA received: {'lab_data': {'partid': '****638', 'assignmentid': '****637', 'courseid': '62825'}}
Unsuccessful vocapi call to start lab
Error: Failed operation: Start. account is still in cleanup, expect another 5 minutes
Initial Lab state: Terminated
Final Lab state after loop: Terminated
AWS Console URL extracted:
AWS credentials file created at /home/coder/.aws/credentials
AWS config file created at /home/coder/.aws/config
Running the vocapi_call_get_aws_console_url at Thu Jul 10 10:09:47 PM UTC 2025
Current run count: 0
Using LAB_SPACE_ID: fydtitwdhzvo
START_LAB_DATA received: {'lab_data': {'partid': '****638', 'assignmentid': '****637', 'courseid': '62825'}}
--------------------------
--------------------------
vocapi response status: success
Extracted AWS Console URL
AWS Console URL written to /home/coder/.aws/aws_console_url
Run count incremented to: 1
Run count written to /home/coder/vocapi_call_run_count
Starting the 2-hour wait at Thu Jul 10 10:09:50 PM UTC 2025
Starting the vocapi_call_wrapper at Thu Jul 10 10:09:50 PM UTC 2025
Iteration 1 of 8 started at Thu Jul 10 10:09:50 PM UTC 2025
Sleeping for 900 seconds before next iteration...
@arsegorov I refreshed your AWS account, there was permission issue. I hope it’s now resolved for you. Please let me know when you get the chance to try it again.
Yes, it’s working now.
Thank you!