Error: Module not found

Address could not be resolved

╷
│ Error: Module not found
│
│ The module address
│ "[email protected]/your-project/yourpath/modules/module1" could
│ not be resolved.
│
│ If you intended this as a path relative to the current module, use
│ "./[email protected]/your-project/yourpath/modules/module1"
│ instead. The "./" prefix indicates that the address is a relative
│ filesystem path.
╵

Related

• terraform init
• Error: Failed to download module

See also

• Terraform modules, terraform get, module { source }, AWS modules, module., child modules, Terraform modules inputs, submodules, terraform init -upgrade
• terraform init [ -upgrade | -reconfigure | -backend-config | -get-plugins=false | -verify-plugins=false ], --help, Execution examples, Execution with errors, ~/.terraformrc, required_providers
• Terraform, OpenTofu, Terrakube.org, Installation, Terraform AWS, Terraform GCP, Terraform commands, Terraform Cloud, Terraform Enterprise (TFE), HCL, HIL, meta-arguments, providers, modules, resource, provisioners, data sources, backends: remote backends, examples, configuration files, state files, variables, types, Terraform Registry, conditionals: depends_on, functions, Blocks, dynamic blocks, errors, Terragrunt, Terraformer, Terratest, Terraform certifications, Terraform map type, Terraform Associate, Terraform: list type, TF_VAR_, TF_LOG, Terraform provider versioning, Terraform Style Conventions, Required version, Terraform plugin, Terraform Named Values, tags, Changelog, tfsec, tflint, Operators, Expressions: for, splat, Debugging, Namespaces, Terraform Landing Zones, CDKTF, Atmos