AWS Fault Injection Service vs Chaos Mesh
AWS Fault Injection Service
aws.amazon.com
Chaos Mesh
chaos-mesh.orgSide by side
| Figure | AWS Fault Injection Service | Chaos Mesh |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Chaos Engineering Platforms | 8.2 (#6) | 8.6 (#4) |
| Purpose | AWS FIS runs fault injection experiments on AWS workloads to help teams improve application performance, observability, and resilience. | Chaos Mesh simulates faults in development, testing, and production environments to help identify potential system problems. |
Plans
AWS Fault Injection Service
- AWS Fault Injection Service$0.10, paid once
In their own words
AWS Fault Injection Service
AWS Fault Injection Service has no write-up on Specifiction yet; its figures are above.
Chaos Mesh
Chaos Mesh is a free, open-source platform for running fault simulations in development, testing, and production environments. It runs on Kubernetes and manages experiments through Kubernetes CustomResourceDefinitions and the Kubernetes API. Fault simulations cover areas including Pods, networks, DNS, HTTP, I/O, time, stress, kernels, block devices, JVMs, physical machines, and AWS, Azure, and GCP. Schedule, Workflow, and StatusCheck resources support recurring experiments, serial or parallel workflows, and application health checks. Selectors and namespace controls help scope experiments to chosen targets. Chaos Dashboard offers a web interface and HTTP API for creating, managing, and observing experiments, with role-based access control enabled by default. Chaos Mesh is licensed under Apache License 2.0 and can be installed from its Helm repository using Helm 3. Compatibility varies by release: version 2.8 supports Kubernetes 1.30 through 1.35, while version 2.7 supports 1.26 through 1.28. Its privileged Chaos Daemon runs as a Kubernetes DaemonSet by default, though that permission can be disabled. Community support is available through CNCF Slack and GitHub Discussions.