AWS Fault Injection Service review
A focused AWS service for controlled resilience experiments with usage-based pricing.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
AWS Fault Injection Service is a managed chaos engineering service for teams running workloads on AWS. It lets teams define experiment templates with actions, targets, and stop conditions, then run or schedule controlled fault-injection experiments through the AWS console and related interfaces. The service covers AWS resources including Amazon EC2, ECS, EKS, databases, networking, storage, and Systems Manager, with specific support for Kubernetes pod fault injection on Amazon EKS.
Pricing is usage-based rather than subscription-based. Standard action-minute usage starts at $0.10 per action-minute, with an additional $0.10 per action-minute for each additional account outside GovCloud. AWS GovCloud (US-East and US-West) action-minute usage is $0.12 per action-minute, plus $0.12 per action-minute for each additional account. Experiment reports cost $5 per report and summarize experiment actions while capturing application responses from a customer-provided CloudWatch Dashboard. This structure suits teams that want costs tied to experiment activity, but the total depends on action minutes, account scope, and report usage.
Its main strength is controlled disruption within an AWS operating model. Teams can test network latency, packet loss, blackhole conditions, connectivity disruption, and other service-specific failures, while CloudWatch alarm stop conditions and safety levers help stop running experiments or prevent new ones. One-time and recurring scheduling supports repeatable exercises, and orchestrator and target accounts support multi-account experiments. Teams centered on AWS and EKS should find the feature set closely aligned with their environment. Organizations seeking a cloud-agnostic chaos platform or broader cross-provider coverage should choose an alternative.
AWS Fault Injection Service pros and cons
- Where it wins
- Preconfigured faults across AWS services, networking, storage, and databases
- EKS pod injection plus one-time and recurring experiment scheduling
- Safety levers, alarm stop conditions, and multi-account experiments
- Where it doesn't
- Usage costs vary with action minutes, accounts, and reports
- Experiment reports require a customer-provided CloudWatch Dashboard
- Experiment Scheduler is unavailable in AWS GovCloud regions
AWS Fault Injection Service fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update