Terraform AWS OpenSearch
OpenSearch domains with VPC placement, encryption at rest, node to node encryption, fine grained access control, audit logs, TLS enforcement, and snapshot configuration.
Quick start
module "opensearch" {
source = "awswellarchitected.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
# ... your arguments here
}module "opensearch" {
source = "iso27001.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
# ... your arguments here
}module "opensearch" {
source = "pcidss.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
# ... your arguments here
}module "opensearch" {
source = "cfrpart11.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
# ... your arguments here
}module "opensearch" {
source = "rbicybersecurity.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
# ... your arguments here
}module "opensearch" {
source = "nistcsf.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
# ... your arguments here
}module "opensearch" {
source = "nydfs23.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
# ... your arguments here
}module "opensearch" {
source = "eugmpannex11.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
# ... 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 "opensearch" {
source = "terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
}module "opensearch" {
source = "soc2.compliance.tf/terraform-aws-modules/opensearch/aws"
version = "~> 2.11"
}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 "opensearch" {
source = "terraform-aws-modules/opensearch/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 12 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.
Mapped compliance frameworks
| Clause | Controls from this module |
|---|---|
| Data protection | |
| Detection | |
| Identity and access management |
| Clause | Controls from this module |
|---|---|
| A.8.12 Data leakage prevention | |
| A.8.14 Redundancy of information processing facilities | |
| A.8.15 Logging | |
| A.8.16 Monitoring activities | |
| A.8.2 Privileged access rights | |
| A.8.24 Use of cryptography |
| Clause | Controls from this module |
|---|---|
| 1.2.5: Network security controls (NSCs) are configured and maintained. | |
| 10.3.2: Audit logs are protected from destruction and unauthorized modifications. | |
| 10.3.3: Audit log files, including those for externalfacing technologies, are promptly backed up to a secure, central, internal log server(s) or other media that is difficult to modify | |
| 10.3.4: File integrity monitoring or change-detection mechanisms is used on audit logs to ensure that existing log data cannot be changed without generating alerts | |
| 10.5.1: Retain audit log history for at least 12 months, with at least the most recent three months immediately available for analysis | |
| 10.6.3: Time-synchronization mechanisms support consistent time settings across all systems. | |
| 2.2.5: System components cannot be compromised by exploiting insecure services, protocols, or daemons | |
| 2.2.7: System components are configured and managed securely. | |
| 3.2.1: Storage of account data is kept to a minimum. | |
| 3.3.1.1: Sensitive authentication data (SAD) is not stored after authorization. | |
| 3.3.1.3: Sensitive authentication data (SAD) is not stored after authorization. | |
| 3.3.2: Sensitive authentication data (SAD) is not stored after authorization. | |
| 3.3.3: Sensitive authentication data (SAD) is not stored after authorization. | |
| 3.5.1: Primary account number (PAN) is secured wherever it is stored. | |
| 4.2.1.1: An inventory of the entity's trusted keys and certificates used to protect PAN during transmission is maintained | |
| 4.2.1: PAN is protected with strong cryptography during transmission. | |
| 5.3.4: Anti-malware mechanisms and processes are active, maintained, and monitored. | |
| 7.2.1: Access to system components and data is appropriately defined and assigned. | |
| 7.2.2: Access to system components and data is appropriately defined and assigned. | |
| 7.2.5: Access to system components and data is appropriately defined and assigned. | |
| 7.2.6: Access to system components and data is appropriately defined and assigned. | |
| 7.3.1: Access to system components and data is managed via an access control system(s). | |
| 7.3.2: Access to system components and data is managed via an access control system(s). | |
| 7.3.3: Access to system components and data is managed via an access control system(s). | |
| 8.2.7: User identification and related accounts for users and administrators are strictly managed throughout an accounts lifecycle. | |
| 8.2.8: If a user session has been idle for more than 15 minutes, the user is required to re-authenticate to re-activate the terminal or session | |
| 8.3.2: Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components | |
| 8.3.4: Strong authentication for users and administrators is established and managed. | |
| A1.2.3: Processes or mechanisms are implemented for reporting and addressing suspected or confirmed security incidents and vulnerabilities |
| Clause | Controls from this module |
|---|---|
| 11.10(c) Protection of records to enable their accurate and ready retrieval throughout the records retention period | |
| 11.10(e) Use of secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records | |
| 11.10(g) Use of authority checks to ensure that only authorized individuals can use the system, electronically sign a record, access the operation or computer system input or output device, alter a record, or perform the operation at hand | |
| 11.30 Controls for open systems |
| Clause | Controls from this module |
|---|---|
| Annex I (1.3) | |
| Annex I (7.4) |
| Clause | Controls from this module |
|---|---|
| ID.BE-5 | |
| PR.DS-1 | |
| PR.DS-2 | |
| PR.DS-5 | |
| PR.PS-04 | |
| RC.RP-06 |
| Clause | Controls from this module |
|---|---|
| 500.14(a) | |
| 500.15(a) |
| Clause | Controls from this module |
|---|---|
| 17 Archiving | |
| 7.1 Data Storage - Damage Protection |
Framework coverage
Which controls from this module are active under each framework endpoint. Your framework preferences choose the columns.
12 controls enforced with a source URL change.