AWS Fault Injection Service
6.2#10 in chaos engineering platforms$0.10, paid onceWebAPILinuxmacOS
VisitAWS Fault Injection Service vs Krkn
What both publish
| Fact | AWS Fault Injection Service | Krkn |
|---|---|---|
| Integrations | FIS can be accessed through the AWS Management Console, CLI, SDKs, CloudFormation, and HTTPS API, and its APIs can be used in CI/CD pipelines and custom tooling. | The documentation describes integrations with Prometheus, Elasticsearch, Grafana, Slack, S3, and CI/CD systems such as Jenkins and GitHub Actions. |
| Monitoring | FIS supports Amazon CloudWatch metrics for monitoring experiments and shows experiment progress and action details through its console and APIs. | Cerberus monitors Kubernetes and OpenShift health and exposes a go/no-go signal, reports, and a metrics API. |
| Purpose | AWS FIS runs fault injection experiments on AWS workloads to help teams improve application performance, observability, and resilience. | Krkn injects deliberate failures into Kubernetes clusters to test their resilience. |
| Rollback | FIS supports automatically rolling back or stopping an experiment when specified conditions are met. | Krkn’s rollback system persists changes to the filesystem before a scenario so it can restore targeted Kubernetes objects or subsystems. |
AWS Fault Injection Service plans
- AWS Fault Injection Service$0.10, paid once
Krkn plans
- KrknFree
Pick AWS Fault Injection Service if…
FIS suits teams that want to examine how AWS workloads respond to controlled disruptions. It is especially relevant to teams able to plan experiments carefully and use pre-production before production.
Pick Krkn if…
Krkn suits chaos engineers and teams building resilience testing workflows for Kubernetes or OpenShift. Users need cluster-admin kubeconfig access and Docker 20.10+ or Podman 4.0+; standalone Python use requires Python 3.9 and manual dependency management.