AWS Fault Injection Service
Ranked in Chaos Engineering Platforms ·No free plan on record
About
AWS Fault Injection Service (FIS) runs fault-injection experiments on AWS workloads so teams can examine application performance, observability, and resilience. Its Scenario Library includes AWS-created templates for disruptions ranging from partial failures to more severe impacts. Many action types run without agents, but instance-level CPU and memory utilization faults require the SSM agent. Teams can select targets with tags and set CloudWatch alarms or other conditions to stop or roll back experiments automatically. The console and APIs show experiment progress and action details, while CloudWatch metrics support monitoring. FIS is accessible through the AWS Management Console, CLI, SDKs, CloudFormation, and HTTPS API, including for CI/CD pipelines and custom tooling. IAM controls who can run experiments and which resources may be affected; actions taken during experiments generate CloudTrail logs. Experiments affect real AWS resources, so AWS recommends planning them and running them in pre-production before production use. Pricing is 0.10 USD per once, billed per action-minute; additional accounts cost $0.10 per action-minute each. GovCloud (US-East and US-West) rates are $0.12 per action-minute, plus $0.12 per action-minute for each additional account. Reports cost $5 per report.
Who it is for
FIS suits teams that need to exercise AWS workloads and observe how applications respond to disruptions. It also fits teams integrating experiments into CI/CD pipelines or custom tooling.
What is good
- AWS-created templates cover multiple disruption severities
- Tag-based target selection and automatic stop controls
- Console, CLI, SDK, CloudFormation, and HTTPS API access
- IAM controls experiment permissions and affected resources
What to know first
- Experiments act on real AWS resources
- Some CPU and memory faults require the SSM agent
- Experiment reports cost $5 per report
Verdict
FIS provides experiment templates, monitoring, and controls for fault injection on AWS resources. Teams should account for per-action-minute charges and plan experiments carefully, as actions affect real resources.
Compared on chaos engineering platforms
- Kubernetes support
- Yesaws.amazon.com
- Cloud fault injection
- Yesaws.amazon.com
- Network fault injection
- Yesaws.amazon.com
- Experiment scheduling
- Yesaws.amazon.com
- Deployment model
- cloudaws.amazon.com
- Blast-radius controls
- Yesaws.amazon.com
Facts
- Purpose
- AWS FIS runs fault injection experiments on AWS workloads to help teams improve application performance, observability, and resilience.aws.amazon.com · 3 Oct 2026
- Managed service
- FIS is fully managed and its experiments can run without installing agents for many action types.aws.amazon.com · 3 Oct 2026
- Agent exception
- Instance-level CPU and memory utilization faults require the SSM agent.aws.amazon.com · 3 Oct 2026
- Scenario library
- The FIS Scenario Library provides AWS-created experiment templates for testing disruptions ranging from partial failures to more severe impacts.aws.amazon.com · 3 Oct 2026
- Safety controls
- Experiments can use tags to select targets and CloudWatch alarms or other tools to stop an experiment when conditions are met.aws.amazon.com · 3 Oct 2026
- Rollback
- FIS supports automatically rolling back or stopping an experiment when specified conditions are met.docs.aws.amazon.com · 3 Oct 2026
- Monitoring
- FIS supports Amazon CloudWatch metrics for monitoring experiments and shows experiment progress and action details through its console and APIs.aws.amazon.com · 3 Oct 2026
- 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.docs.aws.amazon.com · 3 Oct 2026
- Audit trail
- AWS states that FIS generates CloudTrail logs for actions it takes on AWS resources during an experiment.aws.amazon.com · 3 Oct 2026
- Access security
- FIS integrates with AWS Identity and Access Management to control who can run experiments and which resources and services can be affected.aws.amazon.com · 3 Oct 2026
- Transport security
- FIS API clients must support TLS 1.2, and AWS recommends TLS 1.3.docs.aws.amazon.com · 3 Oct 2026
- Operational scope
- For a single-account experiment, target resources must be in the experiment's AWS account; multi-account experiments can target resources in other accounts.docs.aws.amazon.com · 3 Oct 2026
- Real resource effects
- FIS carries out real actions on real AWS resources, and AWS recommends planning experiments and running them in pre-production before production use.docs.aws.amazon.com · 3 Oct 2026
- Report charge
- Experiment reports summarizing actions and application response from a customer-provided CloudWatch Dashboard cost $5 per report.aws.amazon.com · 3 Oct 2026
Best AWS Fault Injection Service alternatives
See all 20
Where it ranks on Inferse
Sources
- aws.amazon.com/fis/features/· checked 3 Oct 2026
- aws.amazon.com/fis/faqs/· checked 3 Oct 2026
- docs.aws.amazon.com/fis/latest/userguide/what-is.html· checked 3 Oct 2026
- docs.aws.amazon.com/fis/latest/userguide/infrastructure-sec· checked 3 Oct 2026
- aws.amazon.com/fis/pricing/· checked 3 Oct 2026