When i run:-
terraform apply -target=module.transform_job
i log the following error:-
Error: creating Glue Catalog Database (de_c4w4a2_silver_db): operation error Glue: CreateDatabase, https response error StatusCode: 400, RequestID: ea856439-6b56-43a7-958e-039d620d7187, AlreadyExistsException: Database already exists.
with module.transform_job.aws_glue_catalog_database.transform_db,
on modules/transform_job/glue.tf line 1, in resource “aws_glue_catalog_database” “transform_db”:
1: resource “aws_glue_catalog_database” “transform_db” {
But the problem is this database does not exist in the glue.
So I checked using the following:-
aws glue get-database --name de_c4w4a2_silver_db
which yielded this error:-
and got an error:- An error occurred (AccessDeniedException) when calling the GetDatabase operation: Insufficient Lake Formation permission(s) on de_c4w4a2_silver_db
I am unable to grant this database the required permission please help.
My coursera subscription will expire in 4 days I really don’t want to buy another subscription just to complete one last assignment considering the course is already 99% done.
Hi,
Kindly request a lab refresh using this form.
You’ll receive a notification once it’s completed. Thanks!
I applied for the refresh and my lab did get refreshed and all three terraform commands now work but terraform apply -target=module.transform_job shows the following results:-
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
╷
│ Warning: Resource targeting is in effect
│
│ You are creating a plan with the -target option, which means that the result of this plan may not represent all of the changes requested by
│ the current configuration.
│
│ The -target option is not for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or
│ when Terraform specifically suggests to use it as part of an error message.
╵
╷
│ Warning: Applied changes may be incomplete
│
│ The plan was created with the -target option in effect, so some changes requested in the configuration may have been ignored and the output
│ values may not be fully updated. Run the following command to verify that no other changes are pending:
│ terraform plan
│
│ Note that the -target option is not suitable for routine use, and is provided only for exceptional situations such as recovering from
│ errors or mistakes, or when Terraform specifically suggests to use it as part of an error message.
╵
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
Outputs:
glue_api_users_extract_job = “de-c4w4a2-api-users-extract-job”
glue_rds_extract_job = “de-c4w4a2-rds-extract-job”
glue_role_arn = “arn:aws:iam::652364515135:role/de-c4w4a2-glue-role”
glue_sessions_users_extract_job = “de-c4w4a2-api-sessions-extract-job”
When I run these three jobs from command line:-
glue_api_users_extract_job
glue_sessions_users_extract_job
glue_rds_extract_job
It shows the following error occurs:-
An error occurred (AccessDeniedException) when calling the StartJobRun operation: User: arn:aws:sts::652364515135:assumed-role/voclabs/user4161362=xjlfpinlzjvv is not authorized to perform: glue:StartJobRun on resource: arn:aws:glue:us-east-1:652364515135:job/glue_rds_extract_job because no identity-based policy allows the glue:StartJobRun action
So I go to the console and open the glue menu and run the three ETL jobs from there and they successfully run but I could not find glue_json_transformation_job and glue_songs_transformation_job anywhere in the ETL menu and when I try to execute from command line it shows the following error:-
An error occurred (AccessDeniedException) when calling the StartJobRun operation: User: arn:aws:sts::652364515135:assumed-role/voclabs/user4161362=xjlfpinlzjvv is not authorized to perform: glue:StartJobRun on resource: arn:aws:glue:us-east-1:652364515135:job/glue_json_transformation_job because no identity-based policy allows the glue:StartJobRun action
Hi @hawraa.salami,
@ANAND_KASHYAP is encountering an authorization error following the recent lab refresh. When you have a moment, could you please take a look?
Thanks so much!