New Feature: Private Module Registry Namespaces
Private module registry namespaces allow you to organize Terraform and OpenTofu modules easier and select which environments to share them with.
Scalr has long had a private module registry for standardizing how teams consume Terraform and OpenTofu modules. Until now, a registry lived either at the account scope or inside a single environment. That worked, but it gave you little control over how modules were grouped and who could see them. Module namespaces fix that.
What are Module Registry Namespaces?
A namespace is a top-level registry for your modules inside a Scalr account. It gives you a place to group modules however your organization is structured, whether that's by team, by project, or by some other line you draw. You are no longer stuck creating registries only at the account scope or inside a single environment. You create a namespace and assign it to the whole account or to a set of environments you pick.
What's Different from the Old Module Registry Concept?
Previously, modules could only be published directly to either the account scope (making them available to all environments and workspaces) or within a specific environment scope (limiting them to that environment). While this worked, it lacked the flexibility needed for larger, more complex organizations.
With namespaces, you now get the following:
- Centralized Namespace Creation: Namespaces are now only created at the account scope. This establishes a clear, top-level organizational layer for all your modules.
- Flexible Sharing, Not Just Scope: Instead of a module being strictly account-wide or environment-specific by its creation location, a namespace owner can now choose to share the namespace with all environments or select environments. This provides far more granular control over module visibility and access.
- Namespace Ownership: Optionally, namespaces can have team ownership assigned to them, and only that team will be able to manage them.
Existing Module Registries
All your existing module URLs remain fully functional after the migration to namespaces. Any existing module calls using the previous account or environment scope will continue to work without changes. Your current IaC workflows will not be disrupted.
Get Started Today!
Module registry namespaces are available now in all Scalr accounts. If you manage a lot of modules, it's worth setting up a namespace or two and seeing how the grouping works for your teams.
For steps on how to create and manage namespaces, see our updated documentation: https://docs.scalr.io/docs/private-module-registry
Frequently asked questions
What are module registry namespaces in Scalr?
A namespace is a top-level registry for Terraform and OpenTofu modules inside a Scalr account. It lets you group modules by team, project, or any other line your organization draws, and share each namespace with the whole account or with a set of environments you pick.How are namespaces different from Scalr's old module registry scopes?
Previously modules were published either at the account scope, making them visible to all environments, or inside a single environment. Namespaces are created only at the account scope and then shared with all or selected environments, which gives more granular control over module visibility. Namespaces can also have team ownership, so only that team can manage them.Do existing Scalr module URLs break after moving to namespaces?
No. All existing module URLs remain fully functional after the migration to namespaces, and module calls that use the previous account or environment scope keep working without changes, so current IaC workflows are not disrupted.Which Scalr accounts have access to module registry namespaces?
Module registry namespaces are available in all Scalr accounts. Steps for creating and managing namespaces are covered in the Scalr private module registry documentation.
Terraform Modules Explained
A comprehensive guide to understanding, creating, and managing Terraform modules for scalable Infrastructure as Code.