I am a bit new to terraform and I am trying to do the following. This could be incorrect or a flawed approach so feel free to correct me or suggest an alternate approach.

Our company wants to start creating aurora DBs in AWS using Terraform.

I want to create a template (module) that uses a public registry module as its source, specifically rds-aurora. I then want to add some company specific config and overwrite some defaults.

Then I want to source THAT template (module) in a different folder on a customer by customer basis with more config respective to that customer.

Public Aurora Module (rds-aurora) -> Base Company Aurora Template (module) -> Customer Aurora Template (module)

The main issues is that while Base Company Aurora Template recognizes all the rds-aurora fields, Customer Aurora Template does not and will complain about them. It seems to think its a different type.

For example, if I try to specify a serverless field from the registry module in my Customer Aurora Template

An argument named "serverlessv2_scaling_configuration" is not expected here.

Surely there must be a way to tell the module in Customer Aurora Template that it is a rds-aurora type? Or maybe that is beyond the scope of Terraform. I suppose I could fork the repo into its own folder and expand off that if it came to it, but I would like to know if this is possible.