my glue jobs are failing constantly from 2-3 days due to which i am unable to complete the lab. can someone reset this lab fully including the aws resources so that i can complete this lab. it is getting really frustrating. Sorry for inconvenience. Also my terminal is also shutting down abruptly.
It sounds really frustrating — Glue jobs failing for days usually indicates an environment issue rather than something you did wrong. Since the lab resources are often provisioned with tight limits, a clean reset is usually the best way to fix persistent Glue or terminal crashes.
I recommend opening a ticket or asking the course moderators to fully reset your lab environment, including all AWS resources. That typically clears out stale IAM roles, hung Glue sessions, and any orphaned compute that may be causing the failures. Once the environment is rebuilt, your Glue jobs and terminal should behave normally again.
Hang in there — this kind of issue is common in shared lab setups, and a reset almost always resolves it. Let us know once it’s reset if you still run into problems.
Do labs and aws resources reset automatically after a period of time or do we need to contact course moderators to reset it? Is there any way to do it by ourself?
Hi Zura,
In most courses, lab environments and AWS resources do not reset automatically — they typically persist until a reset is requested. Some platforms provide a “Restart Lab” or “Reset Workspace” button in the interface, which can restore the original setup without contacting moderators.
If your platform doesn’t offer a self-service reset, you’ll need to contact the course moderators to reset the lab and associated AWS resources. That’s usually the fastest way to ensure Glue jobs, S3 buckets, and IAM roles are returned to a clean state.
Pro tip: before running ETL jobs again, double-check that the lab shows all expected tables and schemas, so you avoid partial state issues.
will the problem be solved by reboot lab option? And how do i contact course moderator for this course
Hi @Zura can you check AWS console in the glue jobs and let me know what you see there?
i deleted the jobs earlier through aws console and i think i have messed up the whole lab. there were 5 jobs that i deleted
You can start from scratch; you don’t need to restart AWS. You can begin the assignment again, going step by step. This is a great learning opportunity, as these issues are similar to those you will encounter in real-world situations.
Start from scratch, redo the lab carefully, reading each line, go step by step, and let me know how that goes.
Once you start work, your current AWS session will time-out and be erased after a few hours of sitting idle.
This is entirely different than getting a fresh copy of the assignment and starting over.
There are total 5 glue jobs, first 3 executed this time but last 2 failed.
also have I set the date correctly?
do i have to type date in yyyy-MM-dd or leave it as it is
Yes! the date is correct.
So the error I was getting during running my glue job was this
Then I checked my s3 bucket in aws console and checked if the path existed
de-c4w4a1-**********-us-east-1-data-lake/landing_zone/api/users/2025-11-27. This is the path that existed. Therefore I had to change the ingest date in glue.tf and rerun the code cells to place the resources in correct s3 bucket subdirectory. After that the glue jobs succeeded. Therefore if you are getting this particular error then there is a problem with the date you are setting as ingestion date. To set the correct date check your s3 bucket subfolders for the correct date. Thank you for the support.
1 Like