Skip to main content

EC2 process kill


EC2 process kill fault kills the target processes running on an EC2 instance. This fault disrupts the application critical processes such as databases or message queues running on the EC2 instance by killing their underlying processes or threads.

EC2 Process Kill

Use cases

EC2 process kill determines the resilience of applications when processes on EC2 instances are unexpectedly killed (or disrupted).

  • Kubernetes version 1.17 or later is required to execute the fault.
  • The EC2 instance should be in healthy state
  • The target processes should exist in the VM.
  • SSM agent is installed and running in the target EC2 instance.
  • The Kubernetes secret should have the AWS Access Key ID and Secret Access Key credentials in the CHAOS_NAMESPACE. Below is the sample secret file:
    apiVersion: v1
    kind: Secret
    name: cloud-secret
    type: Opaque
    cloud_config.yml: |-
    # Add the cloud AWS credentials respectively
    aws_access_key_id = XXXXXXXXXXXXXXXXXXX
  • We recommend you use the same secret name, that is, cloud-secret. Otherwise, you will need to update the AWS_SHARED_CREDENTIALS_FILE environment variable in the fault template, and you won't be able to use the default health check probes.
  • Go to the common tunables to tune the common tunables for all the faults.
  • Go to AWS named profile for chaos to use a different profile for AWS faults and the superset permission/policy to execute all AWS faults.

Below is an example AWS policy to execute the fault.

"Version": "2012-10-17",
"Statement": [
"Effect": "Allow",
"Action": [
"Resource": "*"
"Effect": "Allow",
"Action": [
"Resource": "*"
"Effect": "Allow",
"Action": [
"Resource": [

Fault tunables

Mandatory tunables

Tunable Description Notes
EC2_INSTANCE_ID ID of the target EC2 instance. For example, i-044d3cb4b03b8af1f.
REGION The AWS region ID where the EC2 instance has been created. For example, us-east-1.
PROCESS_IDS Process IDs of the target processes provided as comma-separated values. For example, 183,253,857.

Optional tunables

Tunable Description Notes
TOTAL_CHAOS_DURATION Duration that you specify, through which chaos is injected into the target resource (in seconds). Defaults to 30s.
RAMP_TIME Period to wait before and after injecting chaos (in seconds). For example, 30

Process IDs

Target process IDs running on a particular EC2 instance.

The following YAML snippet illustrates the use of this environment variable:

# Process kill running on EC2 instance
kind: ChaosEngine
name: engine-nginx
engineState: "active"
chaosServiceAccount: litmus-admin
- name: ec2-process-kill
# List of Process IDs
value: '8688,4678'
value: 'instance-1'
- name: REGION
value: 'us-west-2'