Skip to content
This repository has been archived by the owner on Aug 28, 2024. It is now read-only.

Latest commit

 

History

History
70 lines (46 loc) · 3.28 KB

README.rst

File metadata and controls

70 lines (46 loc) · 3.28 KB

Chaos Injection for Amazon EC2 instances or containers using SSM

Issues Maintenance Twitter

Collection of SSM Documents. This allows to conduct small chaos engineering experiments for your Amazon EC2 instances and container based applications in the AWS Cloud.

To learn how to use these SSM Documents - 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

Upload all of the SSM Documents to the AWS region of your choice

git clone [email protected]:adhorn/chaos-ssm-documents.git

cd chaos-ssm-documents

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

Upload one document at a time

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

SOME WORDS OF CAUTION BEFORE YOU START BREAKING THINGS:

  • 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.

More information:

Please read the following Blog post to understand in details how to use these SSM Documents.