If you decide to use the Bees, please keep in mind the following important caveat: they are, more-or-less a distributed denial-of-service attack in a fancy package and, therefore, if you point them at any server you don’t own you will behaving unethically, have your Amazon Web Services account locked-out, and be liable in a court of law for any downtime you cause.
You have been warned.
Create a config file bees.yaml with the following key/values:
key-name: Your key pair name for EC2 (required!)servers: How many servers you want (default: 5)group: EC2 security group (default: public)zone: EC2 zone (default: us-east-1d)image-id: EC2 image id (default: ami-ff17fb96)username: (default: newsapp, don't change this...)
Create a battleplan (<planname>.yaml) file with the following key/values:
script: (Local) path to script to use for attackrequirements: A pip requirements file for the environment.users: Amount of users (total)ssl-ratio: Ratio of users that connect via SSL (float)messages: How many messages to send (total)min-pause: Minimum pause (in seconds) between messagesmax-pause: Maximum pause (in seconds) between messagesmin-length: Minimum length of messagesmax-length: Maximum length of messagestarget-host: Hostname of the target servertarget-port: Port of the target servertarget-ssl-port: SSL port of the target servertarget-channel: Channel to connect to on the target serverpassword: Password for users to auth
The attack script is called with the following arguments (in order):
- Amount of connections this bee should open
- Ratio of users that should connect via SSL (float)
- Amount of messages this bee should send
- Minimum pause between messages (in seconds, float)
- Maximum pause between messages (in seconds, float)
- Minimum length of messages
- Maximum length of messages
- Host name of the IRC server
- Port on the IRC server
- SSL port on the IRC server
- Target channel
- Password
- Bee ID (number)