Standardize Cloud Resources with Approved Modules
Text size
Standardize Cloud Resources with Approved Modules
Goal: every S3 bucket, database or network your teams create comes from a module your platform team approved, at a version you control.
Without StackGen, modules live in many repositories, teams copy and modify them, and nobody knows which version runs where.
With StackGen, approved modules live in one Module Registry. Teams can only add what the registry offers, governance can block anything else, and you can see which appStacks use each module version.
Steps
- Import your modules. In the Module Registry, select Import Module and import from a Git repository or the Terraform Registry. To import many at once, use the CLI. See Module Registry and Upload custom modules with the CLI.
- Or write new ones. Build a module in the Module Editor, test it, and publish it. See Module Editor.
- Scan them. Check modules against your security policies. See Module compliance scanning.
- Control versions and visibility. Publish semantic versions, label them, and choose whether a module is shared with the whole enterprise or specific workspaces. See Labels and Module access.
- Restrict everything else. Add Module Restriction Policies to a governance configuration so appStacks can only use approved modules and versions. See Module restriction policies.
- Pin Terraform and provider versions. See Terraform and provider versions.
When a module changes
Publish a new version of the module rather than editing the published one. See Create Custom Module Versions, and Edit and sync appStack-owned modules for modules that belong to a single appStack.
What you get
- One source of truth for infrastructure building blocks.
- Security fixes made once, in the module, and rolled out by version.
- A clear view of which modules and versions each team uses.