AWS Fault Injection Simulator is an entirely controlled fault injection service that facilitates the process of discovering app vulnerabilities to elevate its operation, observability, and resiliency.
AWS Fault Injection Simulator incorporates top chaos engineering practices making it simple to build and run fault injection experiments, without the need to work with any agents. For starters, companies can utilize Sample experiments. Fault injection actions, such as stopping an instance, throttling an API, or stopping a cron process, are effectively used to deploy and manage the instances of such actions. The tool is compliant with Amazon CloudWatch for easy synchronization of your metrics to watch for the experiments.
Simplistic scenarios can provide insufficient coverage of real-life conditions that provoke premature, unforeseen failure. That is why simultaneously cropping resources of a different type are supported through the Simulator. Resources that are affected by those fault types can be randomized and custom fault types can be created and managed using AWS Systems Manager.
Experiments in live environments are facing the risk of unintended impact. To keep your fault injection experiments organized and guarded, AWS allows you to set targeting basing on environments, apps, and other dimensions applying tags. For instance, you can enhance CPU usage on 10% of your instances with the tag “environment”:“prod”. In addition, you can limit or stop an experiment by setting rules in the Simulator based on CloudWatch Alarm. For instance, all experiments that take place on a website will come to a complete halt if a web page’s response time is less than an acceptable threshold.
AWS Fault Injection Simulator is united with AWS Identity and Access Management (IAM)for better control over which users/resources have authority to access and run experiments, and which resources/services can be affected.
The Simulator’s console and APIs serve to ensure visibility during each stage of an experiment. During the experiment, you can observe what actions were performed. Once the experiment is finished, you can view detailed information about what actions were taken, whether the stop states were triggered, how metrics are different from the expected steady-state, etc. To maintain correct operational metrics and efficient troubleshooting, you can also determine which resources/APIs are affected by the experiment.
Console and programmatic access
AWS Fault Injection Simulator can be used with the AWS Management Console, AWS CLI, and AWS SDKs. The APIs provide programmatical access to the service for integrating fault injection testing into the CI/CD pipeline, and custom toolset.