MODULO-4 (Tareas de programación: Tarea 3: Creación de canalizaciones de datos por lotes y de flujo continuo de extremo a extremo basadas en los requisitos de las partes interesadas)

Please, I need help. I had internet issues and didn’t finish the workshop. I reached the two-hour limit and couldn’t continue. Please help me reactivate the workshop so I can submit this activity. That’s all I need to complete the course. Thank you.

Por favor, necesito ayuda. Tuve problemas con internet y no terminé el taller. Llegué al límite de dos horas y no pude continuar. Por favor, ayúdenme a reactivar el taller para poder enviar esta actividad. Eso es todo lo que necesito para completar el curso. Gracias.

Hello @Jose_123456789,

Sorry for the inconvenience, I guess you are in last week’s assignment of Course 1. Unfortunately after the lab session expires you need to perform the same steps, to successfully run the glue job, create the vector-db and finally deploy the streaming pipeline.

In order to do that you need to uncomment with the same order the main.tf and outputs.tf files. I suggest to safely delete the whole terraform folder and use get latest version to recreate it. Click help at top right corner and use get latest version then reboot. Hope it helps

Hi Jorge, thank you so much for responding. I followed all the steps you indicated, but the error keeps appearing and won’t let me continue. I’m worried because it’s the only assignment I need to complete the course.

Hello @Jose_123456789,

The issue with terraform crashing has to do with existing resources. You could run terraform apply -no-color 2> errors.txt instead of terraform apply . That will create a errors.txt file that will show info about the terminal crash.:

Then you could go to AWS console and find and delete those resources:

de-c1w4-ml-db in AWS glue > databases
de-c1w4-rds-connection in AWS glue > connections
de-c1w4-glue-role in IAM > roles

You could run terraform apply -no-color 2> errors.txt again and if there is a crawler you need to delete it as well. You could find it in AWS Glue > crawlers:

If the issue continues you could wait a few hours for a new lab session or you could submit this form for a lab refresh. Note it takes 1-2 business days since it is a manual process performed by the engineers Hope it helps