Alternatives to HashiCorp Enos

AWS CloudFormation

CloudFormation suits teams managing AWS infrastructure through templates, from a single EC2 instance to complex multi-Region applications.

Conftest suits developers and platform teams who need to check structured configuration against policies in CI.

kube-score suits teams reviewing Kubernetes definitions for security and resilience concerns, especially those using Helm, Kustomize, or CI/CD.

It suits infrastructure developers using a test-driven workflow, including those testing Chef Infra cookbooks.

It suits people validating AWS CloudFormation templates, including teams that want custom rules, structured output, or editor and CI/CD integrations.

cfn-nag suits teams reviewing CloudFormation security on Linux, macOS, or self-hosted systems.

Checkov suits developers and teams scanning infrastructure-as-code for configuration risks, credentials, or compliance checks.

Cinc Auditor

It suits teams running compliance checks and policy-as-code workflows locally or in CI, including teams using AWS, Azure, or GCP.

KICS

KICS suits teams checking Infrastructure as Code in local environments and CI/CD pipelines.

Terratest

It suits teams that write and verify infrastructure code with tools such as Terraform, Packer, Docker, or Kubernetes.

Kubeconform suits teams and individuals who validate Kubernetes manifests locally or in CI, including configurations with custom resources.

It suits teams reviewing Kubernetes manifests for security and production practices, including automated workflows.

OpenSCAP suits government agencies and contractors, businesses, and open-source users who need SCAP-based compliance checks or vulnerability assessment.

It suits infrastructure teams that want agentless configuration and compliance checks expressed as RSpec tests.

Sonobuoy suits Kubernetes operators who need conformance checks, workload diagnostics, or custom cluster tests.

terraform-compliance suits developers and security teams who need readable Terraform policy checks before deployment.

It suits Go developers building or maintaining Terraform providers, including teams running provisioning checks in CI/CD.

TFLint suits Terraform users who want local checks for language issues, cloud-specific configuration errors, or naming and best-practice rules.