Capstone Project Part 1: Error Creating Glue Database (Database Exists)

Course Q&A Data Engineering Data Modeling, Transformation, and Serving
,
1

While running terraform apply in the transform stage of the Capstone Project, I get an error stating that the Glue Database has already been created:
module.transform_job.aws_glue_catalog_database.transform_db: Creating…
╷
│ Error: creating Glue Catalog Database (de_c4w4a1_silver_db): operation error Glue: CreateDatabase, https response error StatusCode: 400, RequestID: ef00f25e-f3cd-4216-ba5d-5830d4711005, AlreadyExistsException: Database already exists.
│
│ with module.transform_job.aws_glue_catalog_database.transform_db,
│ on modules/transform_job/glue.tf line 2, in resource “aws_glue_catalog_database” “transform_db”:
│ 2: resource “aws_glue_catalog_database” “transform_db” {
│
╵

I checked AWS Glue and there is no database shown. I have filled out the request form, but it does not have an option for requesting assistance on this topic (from other posts here, it looks like I need a lab refresh?).

2

Hello @penguinista
Sorry for the inconvenience. You can select any option in the form; the staff will figure this out themselves.

3

Hi, I’m encountering the same issue today while trying to replicate and fix yesterday’s issue of the transform job failing

4

Hello, I have encountered the same issue as well, is there any solution to it?

5

Hello @Pooja648
Can you please fill out this lab refresh form? After it has been refreshed, please try again to see if the issue exists.

6

Thank you!

7

Thank you for the reply! I put in the ticket almost three weeks ago, but have received no notification back that the environment has been reset. How do I follow up? I am now going to have to pay for an additional month (coursera renewed today) just to finish the capstone, which is suboptimal.

8

@penguinista Your account has been already refreshed (on December 19). I’m very sorry for keeping you waiting!
In the form, we ask learners to try again the lab after 2 business days. The team always prioritizes addressing the issues with AWS accounts and tries to resolve issues within 2 business days.

Sorry again! We’ll work on improving our response regarding these issues.
Please let us know if you still have any other issues!