Terraform AWS SSM Parameter
Systems Manager Parameter Store parameters with KMS encryption, parameter policies, versioning, tier selection, and controlled access to application configuration and secret values.
Quick start
module "ssm-parameter" {
source = "nistcsf.compliance.tf/terraform-aws-modules/ssm-parameter/aws"
version = "~> 2.1"
# ... your arguments here
}This module on the compliance.tf registry lists its versions, inputs and outputs. The Get Started guide and Registry Endpoints cover authentication and how to customize the module for your requirements.
Migration from upstream
Already using terraform-aws-modules? Change only the source URL:
module "ssm-parameter" {
source = "terraform-aws-modules/ssm-parameter/aws"
version = "~> 2.1"
}module "ssm-parameter" {
source = "soc2.compliance.tf/terraform-aws-modules/ssm-parameter/aws"
version = "~> 2.1"
}Same arguments. Same outputs. Controls are checked at terraform plan. The Migration Guide has the step-by-step version.
Reversibility
No lock-in. Switch back by reverting the source URL:
module "ssm-parameter" {
source = "terraform-aws-modules/ssm-parameter/aws"
}Run terraform init -upgrade. Terraform state is unchanged: same resource addresses, same provider, no compliance.tf-specific resources. Controls you already applied remain in AWS.
Controls enforced
Up to 1 controls are checked at terraform plan when this module comes from a compliance.tf endpoint. Which ones are active depends on the endpoint; see Framework coverage.
| Control | Retrofit effort |
|---|---|
| SSM parameters encryption should be enabled | Low |
Mapped compliance frameworks
| Clause | Controls from this module |
|---|---|
| PR.DS-01 |
Framework coverage
Which controls from this module are active under each framework endpoint. Your framework preferences choose the columns.
| Control | Cybersecurity Framework v2.0 |
|---|---|
| SSM parameters encryption should be enabled | Enforced |