AWS Fault Injection Simulator
AWS Fault Injection Simulator
AWS Fault Injection Simulator (FIS) API actively injects faults into AWS resources for chaos engineering — terminate instances, add latency, simulate AZ failure.
Built-in 20+ fault actions (EC2 termination, network latency, CPU stress, API throttling, etc.)
Only injects faults within AWS service scope
CreateExperimentTemplate to define an experiment (target + action + stop condition). StartExperiment to execute.
Uptime · 30-day window
GitHub activity
About this API
FIS is AWS's official chaos engineering tool. Chaos engineering's principle: "proactively inject faults into production systems to see how apps respond, find weak points, fix them". Before FIS, teams ran such drills with custom scripts (kill -9 EC2 instances, modify security groups to block networks) — dangerous and ad hoc. FIS standardizes this: define "target X, action Y, safety condition Z" in an experiment template; AWS injects faults in a controlled way when running; auto-terminates when exceeding stop conditions (e.g. error rate > 5%). Rich action library — EC2 termination/stop, API error injection, network latency, CPU/memory stress, AZ unavailability simulation. For teams seriously running production AWS workloads, periodic chaos tests are effective for surfacing latent failures.
What you can build
- 1Game days (team periodically tests app resilience)
- 2Simulate failures in CI tests
- 3Validate disaster recovery mechanisms
- 4Validate auto-scaling triggers properly
Strengths & limitations
Strengths
- Built-in 20+ fault actions (EC2 termination, network latency, CPU stress, API throttling, etc.)
- Safety mechanisms (auto-stop conditions)
- CloudWatch integration for real-time monitoring
Limitations
- Only injects faults within AWS service scope
- Limited support for complex failure scenarios (e.g. partial network partitions)
Example request
curl https://github.com/mermade/aws2openapi/<endpoint>Getting started
CreateExperimentTemplate to define an experiment (target + action + stop condition). StartExperiment to execute.
FAQ
How do I ensure FIS doesn't actually break production?+
Strict stop conditions (CloudWatch alarms) + blast radius control (touch only a small portion of instances at a time) + test in staging first.
Technical details
- Auth type
- unknown
- Pricing
- unknown
- Protocols
- REST
- SDKs
- python, javascript, go, java
- Response time
- 11 ms
- Last health check
- 5/12/2026, 7:36:33 AM
More from Amazon Web Services
AWS IAM Access Analyzer API analyzes IAM resource policies for over-privileged access or external access — proactively surfaces security risks.
Amazon Chime SDK API embeds real-time audio/video calling and chat into apps (meetings, messaging, PSTN calls).
Amazon CloudFront is the AWS CDN and edge service — accelerates static and dynamic content delivery, a standard for web performance.
Amazon CloudSearch is AWS's managed search service (gradually superseded by OpenSearch Service).
CloudWatch Application Insights API auto-detects application problems — intelligently identifies anomalies (slow SQL queries, memory leaks), reducing manual alarm configuration.
AWS Cognito Identity Pools API issues temporary AWS credentials to frontend apps — identity federation, guest users, direct AWS resource access.
Amazon Cognito User Pools deliver managed user signup, login, password reset, and MFA for applications.
Amazon Connect Contact Lens API uses AI to analyze Amazon Connect calls in real time — sentiment, keywords, compliance detection, auto-summary.