Module-3 , Week3 Assignment 2

intro-to-data-engineering-programming/CUafX/assignment-2-good-data-architecture

When attempting the Lab, Under
4.5. Now, click on Edit inbound rules and delete the current rule. Then, add a new rule with the following properties:

  • Port range: 80
  • Source: 0.0.0.0/0
    I created the rule successfully, delete the default rule and also tested the DNS with Port 90. This time , I got the error 503 Gateway error. But I was not graded for this section and was awarded with 20 marks less. Please award 20 marks.

Hi there,

Would you mind sharing the Submission Report, like in the example below? It’ll help us better understand what’s going on:

Hi,

As per grader output, please try accessing the DNS on port 80.

This may be likely the cause of the 503 error.

I edited the inbound rule and created a new rule that allow only Port 80 instead of 0-66635 saved it
Tried accessing the DNS with port 90. This time I got 503 error. I already mentioned that in my post. But even after that I was not graded and awarded 20 marks.

Hi @hawraa.salami @Mubsi,

It looks like @Artha1 isn’t receiving any marks for Task 2 in the grader output, even though the inbound rule for port 80 has been set up.

Just checking—have there been any recent changes to this part of the course?
Would appreciate your usual help. Thanks so much!

@Artha1 Did you make sure you change the port for de-c1w3-alb-sg and not another resource? You need to change the rules for the de-c1w3-alb-sg , not de-c1w3-ec2-sg

Hey All, I am facing repeated Lab issue(s) and getting no support from coursera. I have already messaged through Report an issue.

Hello,

Are the issues related to your previous query above?

Or are these new issues? If so, could you please share more details? Thanks!

Coursera doesn’t handle issues with the course content or grading.

@TMosh, while I agree it is upto the Course provider to take care of the issue(s) and grading. But, I was thinking Coursera need to oversee and step in when there is any issue that goes unresolved and unnoticed. Having done more than 20 through coursera and attempting the coursera with utmost sincertity this is the regard a student has got in this platform.. :frowning:

No, It is related to the Next Lab, Module 4 , Assignment 3 - Building End-to-End Batch and Streaming Data Pipelines Based on Stakeholder Requirements.

Sharing it once again.

Attempted again today [ 23- June -2025, Monday] These are the issue(s) faced.

  1. Lab session did not load in my PC ( Windows 11, Home, Intel(R) Core™ i7-10510U CPU @ 1.80GHz 2.30 GHz, RAM: 20GB)

  2. I tried to load through Incognitio window, did not help. Had to use “Switch to Old experience” after that it loaded.

  3. Lab id: xcoptigbksxe

  4. I was able to connect to de-c1w4-rds, through endpoint : de-c1w4-rds.c18oac00etqi.us-east-1.rds.amazonaws.com using admin/adminpwrd, Port 3306

  5. I was able to use classicmodels

  6. I was able to select and list ratings table with Iimit 20

  7. I modified the main.tf (line1-15) and [output.tf]( (line 2-8) and save - Ctrl+S

  8. I changed to Terraform directory - cd terraform

  9. I ran - terraform init - successfully

  10. ran terraform plan successfully

  11. But when I rain terraform apply - it throwed error

│ Error: creating Glue Catalog Database (de-c1w4-ml-db): operation error Glue: CreateDatabase, https response error StatusCode: 400, RequestID: 321c8fbc-9e88-4c6b-a41f-7ffa9e1b1faa, AlreadyExistsException: Database already exists.

  1. I also ran this script as per Lab guide, c13oder@7c75e280a372:~/project/terraform$ terraform apply -no-color 2> errors.txt

I also see no etljobs after login to aws and visiting AWS Glue --ETL jobs , hence could not start the etljob to get the job id and hence could not check the status

aws glue get-job-run --job-name de-c1w4-etl-job --run-id jr_60ad9c3886ee448f11bd0e3d3c729c24a2460cd35d72a2f662602ebf66f46637 --output text --query "JobRun.JobRunState"I am

  1. When I login to aws with account id: de-c1w4-558328429245

  2. I couldn’t see the AWS Glue etl job:

  3. I was able to navigate to S3 and review the buckets.

  4. when I try to run the Terraform script after modifying the lines main.tf ( 15-27), output.tf( 10-27)

  5. when I try to run the terraform apply got this error

vector database

Error: creating Glue Catalog Database (de-c1w4-ml-db): operation error Glue: CreateDatabase, https response error StatusCode: 400, RequestID: 4e53e7c8-6e43-4643-b6ac-9ccda1f3841c, AlreadyExistsException: Database already exists.

│

│ with module.etl.aws_glue_catalog_database.ml_database,

│ on modules/etl/[glue.tf] line 1, in resource “aws_glue_catalog_database” “ml_database”:

│ 1: resource “aws_glue_catalog_database” “ml_database” {

  1. I was able to get the vector database name: │

“postgres”

  1. I could not get the vector database password.

I am stuck here and would appreciate your help to complete this lab exercise.

Another thing I notice is, after submitting and I reattempt the Lab session, even after rebooting to copy the lab files again. Nothing changes the same issue(s) resurface, It is nor refreshing/reloading the environment. I am getting a feeling nobody is monitoring / supporting deeplearning lab courses for any problem faced while learning. This is a paid course and we are attempting this course among our busy work schedules.

Hope somebody responds at least to this email. I have June 25th as the deadline to submit this lab session, I have completed all the other course related assignments and quizzes. Please noted, in the Previous Lab session, I experienced an issue which caused me 20 marks even after editing inbound rule and setting the port to allow only port 80, also validated by accessing the DNS with port 90 and getting 503 error, still graded for not completing.. Hope some people validate the lab session and help please.

Regards,

Arthanareeswaran

Dear Labsupport, Kindly help me setting up a fresh Lab simulated environment. so that I can attempt and complete the course. I am just asking to provide a fresh Lab simulated environment for Module 4, assignment 3.

Hi,

Apologies for the inconvenience — the course team is actively working to improve the lab experience.

For the issue with inbound port 80, could you please check if you’ve tried the suggested solution shared earlier by a course staff member?

Regarding the AlreadyExistsException error, you can try resetting your lab manually:

  1. Create a new folder and move your current lab files into it (e.g., name it old_files).
  2. Click the question mark icon (top right) in the lab.
  3. Select “Get the latest version.”

Dear Benjamin, I reattempted the Inbound port 80 issue, this time it worked. I also redid the entire assignment and got 100 marks for the 3rd assignment. (attached the lab evidence here)

I will try to create a new folder, move the current lab files into it and try to “Get the Latest version” and attempt it tomorrow. will let you know how it goes.

Thank you for the help.

Regards
Arthanareeswaran

(attachments)

Lab3 assignment- evidence- June 252025.docx (6.44 MB)

1 Like

Dear Benjamin,

  1. I followed your instructions moved all the existing lab files into /home/coder/project/old_files
  2. went into “?” mark to Get the latest version
    3) I saw the message the lab files updated.
    4)I Proceeded with the assignment
    5) At 1.11. To deploy the resources, run the following commands
    Terraform apply throw error
  3. Also when I login to AWS, could not find AWS Glue ETL Jobs
  4. so I could not get to start the job get job runid or find the status
  5. 2.3 Again i got the terraform apply error "Already Exist Exception
  6. 2.5 I could not get the vector database password, got the error “Unexpected argument”
  7. 2.8, 2.9, 2.10 I could not run since I dont have the password in step 9
  8. IN 3.3, I could not configure the VECTOR_DB_PASSWORD
  9. 4.3 Again I got error “Already Exist Exception”.

I have captured all the steps and attached here.

I am really sad that I had to repeat these lab assignment multiple times due to the Lab resource issue.
Please dont give such kind of struggle and bad experience to the students.

Regards,
Arthanareeswaran
.

(attachments)

Copy old_files in Assignment4.docx (7.54 MB)

Dear Arthanareeswaran,

Thank you for your detailed message and for sharing the steps you followed—it’s clear you’ve put in a lot of effort, and I completely understand how frustrating this experience must be.

I’ve done my best to assist, but it appears that the issue involves technical aspects beyond my ability to resolve. Since some of the errors you’re encountering seem to be related to the lab infrastructure itself, I’ll go ahead and tag one of the course staff who will be better equipped to help you troubleshoot further.

@hawraa.salami – would you be able to take a look at this when you have a moment?

Thank you again for your patience. I hope we can resolve this issue for you soon.

Dear Benjamin, @hawraa.salami , I am stuck and unless the Lab infrastructure can work as expected in the Lab guide, I have very less chance to complete as per original plan to complete the course onJune 29th. I have attempted multiple times, recorded the steps and errors in a draft and has shared. Hope somebody listens and bring back the Lab infrastructure supportive to the students.

@Artha1 If at 1.11 the terraform apply is throwing an error, of course you won’t be able to find the glue jobs, and the other steps of the lab won’t work because they all depend on each other. This is because if terraform apply fails, it means that terraform stopped before creating the glue jobs.

I checked your AWS account, and there’s no problem. When you try again the lab,

  • make sure you have repeated all the steps before 1.11,
  • make sure that everything is commented except what is needed to be uncommented for step 1.11 (only lines 1-15 in main.tf and lines 2-8 in outputs.tf should be uncommented)
  • at step 1.11, try:
    • terraform apply || echo "$?"

This will print the error in the terminal.

If you get an error at this step, please don’t continue and share with me the error.

Sure, I will try again today and let you know how it goes.