Could run terraform apply -target=module.serving -no-color 2> errors.txt instead, that will create an errors.txt file that will provide some details about the crash.
You should be able to find those resources in the AWS console and delete them manually. If you can’t find them or delete them after a few hours a new lab session might clear them.
You could request for a lab refresh to reset your lab resources. Thank you
Hello Georgios, I got the same issue. And this happened over a week long. For both assignment1 and assignment2. After I run ‘terraform apply’ stuffs, the terminal crashed first. And I checked errors.txt, which showed like this:
Error: creating Glue Connection (de-c4w4a1-connection-rds): operation error Glue: CreateConnection, https response error StatusCode: 400, RequestID: 6865b15a-7105-4d3f-adbc-99bd7b16679c, 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-c4w4a1-glue-role): operation error IAM: CreateRole, https response error StatusCode: 409, RequestID: 7bec612a-5ed6-41e5-b595-b8c8a316ee4b, EntityAlreadyExists: Role with name de-c4w4a1-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” {
I have already requested refresh the lab once. But this problem still exists. I have no idea how to deal with the terminal crashs again and again.
Just a quick reminder to ensure that all necessary lines are uncommented in the relevant files before deploying the Terraform resources after the lab refresh.
You can refer to a similar issue (e.g., “connection/resource already exists”) discussed in this thread for guidance.
Let me know if this resolves the issue on your end, or if you need any further assistance.