AWS Fault Injection Simulator (AWS FIS) is a managed service that enables you to perform fault injection experiments on your AWS workloads. 

Fault injection is based on the principles of chaos engineering. 

These experiments stress an application by creating disruptive events so that you can observe how your application responds. 

You can then use this information to improve the performance and resiliency of your applications so that they behave as expected. 

AWS FIS provides templates that generate disruptions, and the controls and guardrails that you need to run experiments in production, such as automatically rolling back or stopping the experiment if specific conditions are met. 

Before you use AWS FIS to run experiments in production, we strongly recommend that you complete a planning phase and run the experiments in a pre-production environment. 

You can access  using SDK, CLI, Managment Console & HTTPS API.

Templates

1. To run experiments, you first create an experiment template. 

2. An experiment template is the blueprint of your experiment. 

3. It contains the actions, targets, and stop conditions for the experiment. 

4. While your experiment is running, you can track its progress and view its status. 

5. An experiment is complete when all of the actions in the experiment have run. 

Actions

1. An action is an activity that AWS FIS performs on an AWS resource during an experiment. 

2. AWS FIS provides a set of preconfigured actions based on the type of AWS resource. 

3. Each action runs for a specified duration during an experiment, or until you stop the experiment. Actions can run sequentially or simultaneously (in parallel).

4. Each AWS FIS action has an identifier with the following format: 

   1. aws:service-name:action-type

   2. aws:ec2:stop-instances

5. Parameters:

   1. These parameters are used to pass information to AWS FIS when the action is run. 

6. Types:

   1. Fault injection actions

      1. aws:fis:inject-api-internal-error

      2. aws:fis:inject-api-throttle-error

      3. aws:fis:inject-api-unavailable-error

   2. Wait action

      1. aws:fis:wait

   3. CloudWatch actions

      1. aws:cloudwatch:assert-alarm-state: Verifies that the specified alarms are in one of the specified alarm states.

   4. Amazon EC2 actions

      1. aws:ec2:send-spot-instance-interruptions

      2. aws:ec2:reboot-instances

      3. aws:ec2:stop-instances

      4. aws:ec2:terminate-instances

   5. Amazon ECS actions

      1. aws:ecs:drain-container-instances: Drain the specified percentage of underlying Amazon EC2 instances on the target clusters 

      2. aws:ecs:stop-task: Runs the Amazon ECS API action StopTask to stop the target task. 

   6. Amazon EKS actions

      1. aws:eks:terminate-nodegroup-instance: Runs the Amazon EC2 API action TerminateInstances on the target node group.

   7. Amazon RDS actions

      1. aws:rds:failover-db-cluster: Runs the Amazon RDS API action FailoverDBCluster on the target Aurora DB cluster. 

      2. aws:rds:reboot-db-instances: Runs the Amazon RDS API action RebootDBInstance on the target DB instance. 

   8. Systems Manager actions

      1. aws:ssm:send-command

      2. aws:ssm:start-automation-execution

Targets

1. A target is one or more AWS resources on which AWS FIS performs an action during an experiment. You can choose specific resources, or you can select a group of resources based on specific criteria, such as tags or state.

2. Supports actions for target resources for the following AWS services: EC2, ECS, EKS and RDS

3. When you define a target, you specify the following:

Stop conditions

1. AWS FIS provides the controls and guardrails that you need to run experiments safely on your AWS workloads.

2. A stop condition is a mechanism to stop an experiment if it reaches a threshold that you define as an Amazon CloudWatch alarm. 

3. If a stop condition is triggered while the experiment is running, AWS FIS stops the experiment.

Content

Content

Content