Scenarios in the AWS FIS scenarios library - AWS Fault Injection Service

Scenarios in the AWS FIS scenarios library

Scenarios included in the scenario library are designed to use tags where possible and each scenario describes the required tags in the Prerequisites and How it works sections of the scenario description. You can tag your resources with those pre-defined tags or you can set your own tags using the bulk parameter editing experience (see Using a scenario).

This reference describes the common scenarios in the AWS FIS scenario library. You can also list the supported scenarios using the AWS FIS console.

For more information, see Working with scenarios.

AWS FIS supports the following Amazon EC2 scenarios. These scenarios target instances using tags. You can use your own tags or use the default tags included in the scenario. Some of these scenarios use SSM documents.

  • EC2 stress: instance failure - Explore the effect of instance failure by stopping one or more EC2 instances.

    Target instances in the current region that have a specific tag attached. In this scenario we will stop those instances and restart them at the end of the action duration, by default 5 min.

  • EC2 stress: Disk - Explore impact of increased disk utilization on your EC2 based application.

    In this scenario we will target EC2 instances in the current region that have a specific tag attached. In this scenario you can customize an increasing amount disk utilization injected on targeted EC2 instances for the action duration, by default 5 min for each disk stress action.

  • EC2 stress: CPU - Explore impact of increased CPU on your EC2 based application.

    In this scenario we will target EC2 instances in the current region that have a specific tag attached. In this scenario you can customize an increasing amount of CPU stress injected on targeted EC2 instances for the action duration, by default 5 min for each CPU stress action.

  • EC2 stress: Memory - Explore impact of increased memory utilization on your EC2 based application.

    In this scenario we will target EC2 instances in the current region that have a specific tag attached. In this scenario you can customize an increasing amount of memory stress injected on targeted EC2 instances for the action duration, by default 5 min for each memory stress action.

  • EC2 stress: Network Latency - Explore impact of increased network latency on your EC2 based application.

    In this scenario we will target EC2 instances in the current region that have a specific tag attached. In this scenario you can customize an increasing amount of network latency injected on targeted EC2 instances for the action duration, by default 5 min for each latency action.

AWS FIS supports the following Amazon EKS scenarios. These scenarios target EKS pods using a Kubernetes application labels. You can use your own labels or use the default labels included in the scenario. For more information about EKS with FIS, see Use the EKS pod actions.

  • EKS stress: Pod Delete - Explore the effect of EKS pod failure by deleting one or more pods.

    In this scenario we will target pods in the current region that are associated with an application label. In this scenario we will terminate all matched pods. Re-creation of pods will be controlled by kubernetes configuration.

  • EKS stress: CPU - Explore impact of increased CPU on your EKS based application.

    In this scenario we will target pods in the current region that are associated with an application label. In this scenario you can customize an increasing amount of CPU stress injected on targeted EKS pods for the action duration, by default 5 min for each CPU stress action.

  • EKS stress: Disk - Explore impact of increased disk utilization on your EKS based application.

    In this scenario we will target pods in the current region that are associated with an application label. In this scenario you can customize an increasing amount of disk stress injected on targeted EKS pods for the action duration, by default 5 min for each CPU stress action.

  • EKS stress: Memory - Explore impact of increased memory utilization on your EKS based application.

    In this scenario we will target pods in the current region that are associated with an application label. In this scenario you can customize an increasing amount of memory stress injected on targeted EKS pods for the action duration, by default 5 min for each memory stress action.

  • EKS stress: Network latency - Explore impact of increased network latency on your EKS based application.

    In this scenario we will target pods in the current region that are associated with an application label. In this scenario you can customize an increasing amount of network latency injected on targeted EKS pods for the action duration, by default 5 min for each latency action.

AWS FIS supports the following scenarios for multi-AZ and multi-Region applications. These scenarios target multiple resource types.

  • AZ Availability: Power Interruption - Inject the expected symptoms of a complete interruption of power in an Availability Zone (AZ). Learn more about AZ Availability: Power Interruption.

  • Cross-Region: Connectivity - Block application network traffic from the experiment Region to the destination Region and pause cross-Region data replication. Learn more about using Cross-Region: Connectivity.