Managing Amazon Fault Injection Service experiments - AWS Resilience Hub

Managing Amazon Fault Injection Service experiments

This section describes how to create and run Amazon Fault Injection Service (AWS FIS) experiments in AWS Resilience Hub. You run AWS FIS experiments to measure the resiliency of your AWS resources and the amount of time it takes to recover from application, infrastructure, availability zone, and AWS Region incidents.

To measure resiliency, these AWS FIS experiments simulate disruptions to your AWS resources. Examples of disruptions include network unavailable errors, failovers, stopped processes on Amazon EC2 or AWS ASG, boot recovery in Amazon RDS, and problems with your Availability Zone. When the AWS FIS experiment concludes, you can estimate whether an application can recover from the outage types defined in the RTO target of the resiliency policy.

All the experiments in AWS Resilience Hub are built using AWS FIS and they execute AWS FIS actions. Majority of the AWS FIS experiments invoke Systems Manager automation actions to perform disruptions and monitor the alarms, and other AWS FIS experiments use only AWS FIS automation actions that are customised to specific AWS services (such as Amazon EKS action). For more information about AWS FIS actions, see AWS FIS actions reference.

You can use the AWS FIS experiments in their default state or customize them based on your requirements. AWS FIS experiments can be accessed from either AWS Resilience Hub (Viewing fault injection experiments) or AWS FIS console (AWS FIS) .