Chaos Injection for AWS resources using Amazon SSM Run Command and Automation =========================================================================

Collection of SSM Documents.

These documents let you perform chaos engineering experiments on resources (applications, network, and infrastructure) in the AWS Cloud.

To use SSM Automation, check the link

• Support for (randomly) stopping EC2 instances via API
• Support for (randomly) stopping EC2 instances via AWS Lambda
• Support for (randomly) terminating EC2 instances via API
• Support for detaching EBS volumes from EC2 instances via API (ec2, ebs)
• Support for rebooting RDS instance with proper tags via API
• Support for CPU stress scenario via Run Command

aws ssm create-document --content --name "StopRandomInstances-API" file://stop_random_instance_api.yml --document-type "Automation" --document-format YAML

To use SSM Run Command, please check this link

• Support for latency injection using latency-stress.yml
• Support for latency with delta stress using latency-delta-stress.yml
• Support for CPU burn using spu-stress.yml
• Support for IO stress using io-stress.yml
• Support for memory stress using memory-stress.yml
• Support for network stress using network-corruption-stress.yml
• Support for packet Loss stress using network-loss-stress.yml
• Support for configurable blackhole stress using blackhole-stress.yml
• Support for blackhole S3 stress using blackhole-s3-stress.yml
• Support for blackhole DynamoDB stress using blackhole-dynamo-stress.yml
• Support for blackhole EC2 stress using blackhole-ec2-stress.yml
• Support for blackhole DNS stress using blackhole-dns-stress.yml

cd chaos-ssm-documents/automation

aws ssm create-document --content file://cpu-stress.yml --name "cpu-stress" --document-type "Command" --document-format YAML

cd chaos-ssm-documents/run-command

./upload-document.sh -r eu-west-1 (or other region of your choice)

• To begin with, DO NOT use these chaos injection commands in production blindly!!
• Always review the SSM documents and the commands in them.
• Make sure your first chaos injections are done in a test environment and on test instances where no real and paying customer can be affected.
• Test, test, and test more. Remember that chaos engineering is about breaking things in a controlled environment and through well-planned experiments to build confidence in your application — and you own tools — to withstand turbulent conditions.