EC2-backed and serverless faults

AWS faults are categorized into serverless, EC2-backed, and serverless combined with EC2-backed faults. Links to the respective faults are provided.

Serverless faults

These experiments primarily involve ECS Fargate and aren't dependent on EC2 instances. They focus on altering the state or resources of ECS containers without direct container interaction.

Faults that belong to this category are listed below:

1. ECS Fargate CPU Hog

2. ECS Fargate Memory Hog

3. AWS ECS Invalid Container Image

4. AWS ECS Update Container Resource Limit

5. AWS ECS Update Container Timeout

6. AWS ECS Update Task Role

7. AWS ECS Container Volume Detach

EC2-backed faults

These experiments induce chaos within a container and depend on an EC2 instance. Typically, these are prefixed with "ECS container" and involve direct interaction with the EC2 instances hosting the ECS containers.

Faults that belong to this category are listed below:

1. AWS ECS Agent Stop

2. AWS ECS Container CPU Hog

3. AWS ECS Container HTTP Latency

4. AWS ECS Container HTTP Modify Body

5. AWS ECS Container HTTP Modify Header

6. AWS ECS Container HTTP Reset Peer

7. AWS ECS Container HTTP Status Code

8. AWS ECS Container IO Stress

9. AWS ECS Container Memory Hog

10. AWS ECS Container Network Latency

11. AWS ECS Container Network Loss

12. AWS ECS Instance Stop

EC2-backed and serverless faults

These experiments are versatile and are applicable to both serverless ECS tasks and those backed by EC2 instances. They generally involve task-level chaos or access restrictions without causing direct in-container or in-VM disruptions.

Faults that belong to this category are listed below:

1. AWS ECS Task Stop

2. AWS ECS Task Scale

3. AWS ECS Network Restrict