In C4_W4_Assignment_1.ipynb, i am not getting response as shown below in the screenshit
It shows almost 2 mins. I had to stop it as it was not completing.
Hello @tanmayb,
I could reproduce the issue and it seems in part 2.4. you didn’t update your API Endpoint from CloudFormation which was from a previous session. Could you try updating the endpoint and run the cell again. Thank you
Hi @Georgios,
Thanks for your input. Yes, I was able to move ahead with your solution.
But now I am getting subnet error in one of the glue jobs. Other glue jobs are running fine though. I checked the subnet variable name in terraform file, and it seems to be fine. Would be great if could give me some inputs.
Hello @tanmayb,
I could reproduce the issue after I edited the glue.tf file there is a bug. The rds-extract job uses the physical_connection_requirements and you must have edited the availability zone instead:
physical_connection_requirements {
availability_zone = data.aws_subnet.public_a.availability_zone <--CHANGE id to availability_zone
security_group_id_list = [data.aws_security_group.db_sg.id]
subnet_id = data.aws_subnet.public_a.id
Here is the output I am getting with that error:
right. it worked. thanks.
I am getting this error when running extract glue.tf through terraform apply -no-color 2> errors.txt.
Error: creating Glue Job (de-c4w4a1-api-sessions-extract-job): operation error Glue: CreateJob, https response error StatusCode: 400, RequestID: efe7460c-c758-41d8-9137-02e0de5dfd73, IdempotentParameterMismatchException: Job already submitted with different configuration.
with module.extract_job.aws_glue_job.api_sessions_ingestion_etl_job,
on modules/extract_job/glue.tf line 88, in resource “aws_glue_job” “api_sessions_ingestion_etl_job”:
88: resource “aws_glue_job” “api_sessions_ingestion_etl_job” {
the error seems incomplete and terminal is crashing. what is the issue here?
Hello @tanmayb,
I could reporduce the error that you, like @JavidM had in this post. It seems the IdempotentParameterMismatchException that throws this error because de-c4w4a1-api-sessions-extract-job changed their configuration when you ran them before. A new lab session after a few hours fixes it or just select/delete de-c4w4a1-api-sessions-extract-job that you changed to fix it:
Thanks @Georgios . I was able to move forward. But now I am getting this error in one of transofrom jobs. I am wondering how come “duration” column went missing from extracted data?
The other transoform job “de-c4w4a1-json-transform-job” is running fine.
Hello @tanmayb,
I could reproduce the error when I used one day earlier in todays pacific date "--ingest_date". Could you check again in the transform_job/glue.tf file and use a different "--ingest_date" (e.g. 2025-03-20). Hope it helps
Right! This date was at 2 places. Thanks.
1 Like