chaosmonkey

const (
	// StrategyShutdownInstance shuts down the instance using the EC2 API.
	// This is the classic chaos monkey strategy.
	StrategyShutdownInstance Strategy = "ShutdownInstance"

	// StrategyBlockAllNetworkTraffic removes all security groups from the
	// instance, and moves it into a security group that does not allow any
	// access. Thus the instance is running, but cannot be reached via the
	// network. This can only work on VPC instances.
	StrategyBlockAllNetworkTraffic Strategy = "BlockAllNetworkTraffic"

	// StrategyDetachVolumes force-detaches all EBS volumes from the
	// instance, simulating an EBS failure. Thus the instance is running,
	// but EBS disk I/O will fail.
	StrategyDetachVolumes Strategy = "DetachVolumes"

	// StrategyBurnCPU runs CPU intensive processes, simulating a noisy
	// neighbor or a faulty CPU. The instance will effectively have a much
	// slower CPU. Requires SSH to be configured.
	StrategyBurnCPU Strategy = "BurnCpu"

	// StrategyBurnIO runs disk intensive processes, simulating a noisy
	// neighbor or a faulty disk. The instance will effectively have a much
	// slower disk. Requires SSH to be configured.
	StrategyBurnIO Strategy = "BurnIo"

	// StrategyKillProcesses kills any Java or Python programs it finds
	// every second, simulating a faulty application, corrupted
	// installation or faulty instance. The instance is fine, but the
	// Java/Python application running on it will fail continuously.
	// Requires SSH to be configured.
	StrategyKillProcesses Strategy = "KillProcesses"

	// StrategyNullRoute null-routes the 10.0.0.0/8 network, which is used
	// by the EC2 internal network. All EC2 <-> EC2 network traffic will
	// fail. Requires SSH to be configured.
	StrategyNullRoute Strategy = "NullRoute"

	// StrategyFailEC2 puts dummy host entries into /etc/hosts, so that all
	// EC2 API communication will fail. This simulates a failure of the EC2
	// control plane. Of course, if your application doesn't use the EC2
	// API from the instance, then it will be completely unaffected.
	// Requires SSH to be configured.
	StrategyFailEC2 Strategy = "FailEc2"

	// StrategyFailDNS uses iptables to block port 53 for TCP & UDP; those
	// are the DNS traffic ports. This simulates a failure of your DNS
	// servers. Requires SSH to be configured.
	StrategyFailDNS Strategy = "FailDns"

	// StrategyFailDynamoDB puts dummy host entries into /etc/hosts, so
	// that all DynamoDB communication will fail. This simulates a failure
	// of DynamoDB. As with its monkey relatives, this will only affect
	// instances that use DynamoDB. Requires SSH to be configured.
	StrategyFailDynamoDB Strategy = "FailDynamoDb"

	// StrategyFailS3 puts dummy host entries into /etc/hosts, so that all
	// S3 communication will fail. This simulates a failure of S3. Of
	// course, if your application doesn't use S3, then it will be
	// completely unaffected. Requires SSH to be configured.
	StrategyFailS3 Strategy = "FailS3"

	// StrategyFillDisk writes a huge file to the root device, filling up
	// the (typically relatively small) EC2 root disk. Requires SSH to be
	// configured.
	StrategyFillDisk Strategy = "FillDisk"

	// StrategyNetworkCorruption uses the traffic shaping API to corrupt a
	// large fraction of network packets. This simulates degradation of the
	// EC2 network. Requires SSH to be configured.
	StrategyNetworkCorruption Strategy = "NetworkCorruption"

	// StrategyNetworkLatency uses the traffic shaping API to introduce
	// latency (1 second +- 50%) to all network packets. This simulates
	// degradation of the EC2 network. Requires SSH to be configured.
	StrategyNetworkLatency Strategy = "NetworkLatency"

	// StrategyNetworkLoss uses the traffic shaping API to drop a fraction
	// of all network packets. This simulates degradation of the EC2
	// network. Requires SSH to be configured.
	StrategyNetworkLoss Strategy = "NetworkLoss"
)