I am struggling for more than 5 hours for this terraform error and I have other errors with the same context:
│ Error: creating Glue Connection (de-c4w4a2-connection-rds): operation error Glue: CreateConnection, https response error StatusCode: 400, RequestID: ecfad75c-1505-48e2-ad46-e5bc271bccc1, AlreadyExistsException: Connection already exists.
│
│ with module.extract_job.aws_glue_connection.rds_connection,
│ on modules/extract_job/glue.tf line 2, in resource “aws_glue_connection” “rds_connection”:
│ 2: resource “aws_glue_connection” “rds_connection” {
│
╵
╷
│ Error: creating IAM Role (de-c4w4a2-glue-role): operation error IAM: CreateRole, https response error StatusCode: 409, RequestID: 186e44ba-85c9-4286-9fee-8dc09e59a5ec, EntityAlreadyExists: Role with name de-c4w4a2-glue-role already exists.
│
│ with module.extract_job.aws_iam_role.glue_role,
│ on modules/extract_job/iam.tf line 1, in resource “aws_iam_role” “glue_role”:
│ 1: resource “aws_iam_role” “glue_role” {
Hello @Mohamed_Hussien1,
Sorry for the inconvenience, those resources can be found in AWS console and delete them manually. Could you check in AWS glue in connections there should be de-c4w4a2-connection-rds and in IAM roles there is de-c4w4a2-glue-role choose delete and type the name to confirm. If the issue continues you could ask for a lab refresh with the form. Thank you
I tried to do so from console or manually but I got an error that I am not authorized to delete such resources.
I always get : pi error AccessDeniedException: Insufficient Lake Formation permission(s) on de_c4w4a2_silver_db
Hello @Mohamed_Hussien1,
I see this is strange not able to delete them, please wait for a lab refresh after you fill this form it takes 1-2 business days. Hope it helps
I submitted the form and I tried to resolve the issues myself and I resolved most of them but the last error appears and cannot handle it … As you see below … I tried to search about catalog db on aws glue to delete it but did not find it anyway… if this issue is common , please refer me the solution :
Hello @Mohamed_Hussien1,
I can see that this message de_c4w4a2_silver_db already exists cause terraform apply to crash. If you can’t find it in the AWS console, like other resources. I am afraid you need to wait for the lab refresh after you submitted the form, it takes 1-2 business days(no weekends). Thank you
