Skip to main content

ECS Container Volume Detach

ECS container volume detach provides a mechanism to detach and remove volumes associated with ECS task containers in an Amazon ECS (Elastic Container Service) task.

ECS Container Volume Detach


This experiment primarily involves ECS Fargate and doesn’t depend on EC2 instances. They focus on altering the state or resources of ECS containers without direct container interaction.

Use cases

  • This experiment allows you to test and validate the behavior of your ECS tasks when volumes are detached. You can verify the resilience and performance of your application during volume detachment scenarios, ensuring that the containers continue to function as expected.
  • By detaching volumes, you can safely remove the volume associations from the containers without deleting the volumes themselves.
  • By detaching unnecessary volumes, you can optimize the resource utilization within your ECS tasks. This helps to free up storage space and minimize any potential performance impact associated with unused volumes.


  • Kubernetes >= 1.17
  • ECS cluster running with the desired tasks and containers and familiarity with ECS service update and deployment concepts.
  • Create a Kubernetes secret that has the AWS access configuration(key) in the CHAOS_NAMESPACE. Below is a 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
aws_secret_access_key = XXXXXXXXXXXXXXX

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 may be unable to use the default health check probes.

Permissions required

Here is an example AWS policy to execute the fault.

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

Mandatory tunables

Tunable Description Notes
CLUSTER_NAME Name of the target ECS cluster For example, cluster-1.
SERVICE_NAME Name of the ECS service under chaos For example, nginx-svc.
REGION Region name of the target ECS cluster For example, us-east-1.

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.
CHAOS_INTERVAL Interval between successive instance terminations (in seconds) Defaults to 30s.
AWS_SHARED_CREDENTIALS_FILE Path to the AWS secret credentials Defaults to /tmp/cloud_config.yml.
RAMP_TIME Period to wait before and after injecting chaos (in seconds) For example, 30s.

ECS Container Volume Detach

ECS container volume chaos will detach the volumes for specified chaos duration. Tune it by using the SERVICE_NAME and CLUSTER_NAME environment variable.

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

# Set container image for the target ECS task
kind: ChaosEngine
name: aws-nginx
engineState: "active"
annotationCheck: "false"
chaosServiceAccount: litmus-admin
- name: ecs-container-volume-detach
value: 'test-cluster'
value: 'test-service'
- name: REGION
value: 'us-east-2'
VALUE: '60'