Terraform was giving error about resources it couldn’t recreate, so I tried manually deleting them and I think I accidentally deleted a role that is part of the template, can’t recreate it myself.
Also when I open the vscode it often gets stuck, didn’t do that before, or in other labs.
Can you please completely reset the state of my C4W4 assignment 1? The files, the AWS account, everything. Thanks!
Programming Assignment: Assignment 4: Capstone Project Part 1 - ETL and Data Modeling
Did you submit the form to have your lab refreshed?
There is a link to the form in the course Resources area via the “Course Q&A” forum.
I submitted it now through that form.
Account was reset, I reopened the project.
First time terrform apply crashes, next time terraform plan crashes.
I have the final terraform config files with everything uncommented out since I finished all the steps, but it shouldn’t crash the entire environment!!!
Sorry, I’m not a mentor for that course, so I don’t have any direct recommendations.
A lot of learners have issues with the DE materials. Maybe you can find some tips by browsing for similar forum threads.
Hi there,
It looks like the issue you’re facing might be related to the terraform plan or terraform apply commands. Could you please share the output you’re seeing after running them? That will help us troubleshoot more effectively.
Also, just a quick note—section 4.1.6 in the C4_W4_Assignment_1.ipynb notebook includes a helpful reminder to run a Terraform command if the terminal continues to crash. It might be worth revisiting that step.
Let me know how it goes or if you need any further help!
Hi, I eventually managed to pass the assignments.
Only after adding || echo "$?" to all terminal commands.
This prevents them from crashing and also shows the errors inline.
The “helpful reminder” says to try terraform as usual, and then if it crashes, go back and rerun everything and pipe the errors into a file. Isn’t very helpful if it takes very long to recover from crash.
Also, after terraform crashes it forgets the state, and then it complaints about not being able to create some AWS resources even though it created them earlier. So I had to go manually and delete them one by one until it got back to work.
Nice work troubleshooting and resolving the issue on your own!
Adding || echo "$?" to your terminal commands is a smart way for surfacing silent errors and without crashing the session—a helpful tip for others facing similar problems.
Thanks for sharing—your solution will be a great reference in the future!