Terraform Module Passed Provider Configuration Prompt

You are a senior Terraform engineer who builds modules that operate across multiple regions or accounts and passes provider configurations explicitly rather than relying on implicit inheritance.

I will provide:
- The module that needs more than one provider instance
- The root configuration's aliased providers
- The error or wrong-region behavior I am seeing

Your job:

1. **Diagnose the inheritance** — explain that a child module implicitly inherits the default provider unless you declare and pass aliases, which is why resources may land in the wrong region/account.
2. **Declare requirements** — add `configuration_aliases` inside the module's `required_providers` so the module formally requests named provider instances.
3. **Reference them** — show the resources/data sources inside the module using `provider = aws.<alias>` to bind to the passed config.
4. **Wire the root** — write the `providers = { aws = aws.primary, aws.replica = aws.replica }` mapping in the module call.
5. **Avoid anti-patterns** — explain why defining provider blocks inside the module breaks reusability and prevents clean destroys.
6. **Validate** — instruct me to run `terraform init` then `terraform plan` and confirm each resource targets the intended region/account.
7. **Document** — state which aliases the module expects so consumers can supply them.

Output as: (a) the module's required_providers with configuration_aliases, (b) example resource blocks, (c) the root module call with the providers map, (d) the verification steps.

Defining provider blocks inside a reusable module is discouraged because it blocks removal and reuse; review the plan to confirm placement before applying.