Windows EC2 memory hog

Windows EC2 memory hog induces memory stress on the target AWS Windows EC2 instance using Amazon SSM Run command. The SSM Run command is executed using SSM documentation that is built into the fault. This fault:

• Causes memory exhaustion on the target Windows EC2 instance for a specific duration.

Use cases

Windows EC2 memory hog:

• Causes memory stress on the target AWS EC2 instance(s).
• Simulates the situation of memory leaks in the deployment of microservices.
• Simulates application slowness due to memory starvation, and noisy neighbour problems due to hogging.

note

• Kubernetes >= 1.17 is required to execute this fault.
• The EC2 instance should be in a healthy state.
• SSM agent should be installed and running on the target EC2 Windows instance in the admin mode.
• SSM IAM role should be attached to the target EC2 instance(s).
• Kubernetes secret should have the AWS Access Key ID and Secret Access Key credentials in the CHAOS_NAMESPACE. Below is a sample secret file:

apiVersion: v1
kind: Secret
metadata:
  name: cloud-secret
type: Opaque
stringData:
  cloud_config.yml: |-
    # Add the cloud AWS credentials respectively
    [default]
    aws_access_key_id = XXXXXXXXXXXXXXXXXXX
    aws_secret_access_key = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

• It is recommended to 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.

Here is an example AWS policy to execute the fault.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "ssm:GetDocument",
                "ssm:DescribeDocument",
                "ssm:GetParameter",
                "ssm:GetParameters",
                "ssm:SendCommand",
                "ssm:CancelCommand",
                "ssm:CreateDocument",
                "ssm:DeleteDocument",
                "ssm:GetCommandInvocation",          
                "ssm:UpdateInstanceInformation",
                "ssm:DescribeInstanceInformation"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "ec2messages:AcknowledgeMessage",
                "ec2messages:DeleteMessage",
                "ec2messages:FailMessage",
                "ec2messages:GetEndpoint",
                "ec2messages:GetMessages",
                "ec2messages:SendReply"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeInstanceStatus",
                "ec2:DescribeInstances"
            ],
            "Resource": [
                "*"
            ]
        }
    ]
}

• Refer to AWS Named Profile For Chaos to use a different profile for AWS faults.

Fault tunables

Mandatory fields

Variables	Description	Notes
EC2_INSTANCE_ID	ID of the target EC2 instance.	For example, i-044d3cb4b03b8af1f.
REGION	AWS region ID where the EC2 instance has been created.	For example, us-east-1.

Optional fields

Variables	Description	Notes
TOTAL_CHAOS_DURATION	Duration to insert chaos (in seconds).	Defaults to 30s.
AWS_SHARED_CREDENTIALS_FILE	Path to the AWS secret credentials.	Defaults to /tmp/cloud_config.yml.
INSTALL_DEPENDENCIES	Install dependencies to run the network chaos. It can be 'True' or 'False'.	If the dependency already exists, you can turn it off. Defaults to True.
MEMORY_CONSUMPTION	Amount of memory to be consumed by the EC2 instance (in megabytes).	Defaults to 0MB.
MEMORY_PERCENTAGE	Amount of memory to be consumed by the EC2 instance (in percentage).	Defaults to 50.
SEQUENCE	Sequence of chaos execution for multiple instances.	Defaults to parallel. Supports serial and parallel.
RAMP_TIME	Period to wait before and after injecting chaos (in seconds).	For example, 30s.

Memory consumption in megabytes

It specifies the amount of memory to be utilized (in megabytes) on the EC2 instance. Tune it by using the MEMORY_CONSUMPTION environment variable.

Use the following example to tune memory consumption in MB:

# memory in mb to utilize
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: windows-ec2-memory-hog
    spec:
      components:
        env:
        - name: MEMORY_CONSUMPTION
          VALUE: '1024'
        # ID of the EC2 instance
        - name: EC2_INSTANCE_ID
          value: 'instance-1'
        # region for the EC2 instance
        - name: REGION
          value: 'us-east-1'

Memory consumption by percentage

It specifies the amount of memory (in percentage) to be utilized on the EC2 instance. Tune it by using the MEMORY_PERCENTAGE environment variable.

Use the following example to tune memory consumption in percentage:

# memory percentage to utilize
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: windows-ec2-memory-hog
    spec:
      components:
        env:
        - name: MEMORY_PERCENTAGE
          value: '50'
        - name: MEMORY_CONSUMPTION
          value: '0'
        # ID of the EC2 instance
        - name: EC2_INSTANCE_ID
          value: 'instance-1'
        # region for the EC2 instance
        - name: REGION
          value: 'us-east-1'

Multiple EC2 instances

It specifies multiple EC2 instances as comma-separated IDs that are targeted in one chaos run. Tune it by using the EC2_INSTANCE_ID environment variable.

Use the following example to tune multiple EC2 instances:

# multiple instance targets
apiVersion: litmuschaos.io/v1alpha1
kind: ChaosEngine
metadata:
  name: engine-nginx
spec:
  engineState: "active"
  chaosServiceAccount: litmus-admin
  experiments:
  - name: windows-ec2-memory-hog
    spec:
      components:
        env:
        # ids of the EC2 instances
        - name: EC2_INSTANCE_ID
          value: 'instance-1,instance-2,instance-3'
        # region for the EC2 instance
        - name: REGION
          value: 'us-east-1'