Skip to content

Neptune DB clusters should have deletion protection enabled

This control checks if a Neptune DB cluster has deletion protection enabled. The control fails if a Neptune DB cluster doesn't have deletion protection enabled.

How to fix

Attribute deletion_protection of aws_neptune_cluster must be true.

Implementation options

Choose the option that matches how you manage Terraform. All options satisfy this control.

Option 1: Terraform AWS provider resources

If you manage resources directly, configure the relevant Terraform AWS provider resources to meet this control. See docs for the resources involved: aws_neptune_cluster.

resource "aws_neptune_cluster" "this" {
  backup_retention_period        = 7
  cluster_identifier             = "pofix-example"
  enable_cloudwatch_logs_exports = ["audit"]
  skip_final_snapshot            = true

  deletion_protection = true
}
Which option should I choose?
  • Compliance.tf module (recommended): controls enforced by default and mapped to frameworks.
  • Open source module (terraform-aws-modules): compatible by design with compliance.tf. Same variable names for an easy, low-change migration path when you are ready.
  • Terraform AWS provider resources: manage Terraform resources directly.

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf (CTF) Control: neptune_db_cluster_deletion_protection_enabled

  • AWS Config Managed Rule: NEPTUNE_CLUSTER_DELETION_PROTECTION_ENABLED

  • Checkov Check: CKV2_AWS_58

  • Powerpipe Control: aws_compliance.control.neptune_db_cluster_deletion_protection_enabled