diff --git a/charts/kube-aws/ebs-loss/ebs-loss.chartserviceversion.yaml b/charts/kube-aws/ebs-loss/ebs-loss.chartserviceversion.yaml
new file mode 100644
index 0000000..15d8fb1
--- /dev/null
+++ b/charts/kube-aws/ebs-loss/ebs-loss.chartserviceversion.yaml
@@ -0,0 +1,45 @@
+apiVersion: litmuchaos.io/v1alpha1
+kind: ChartServiceVersion
+metadata:
+  createdAt: 2020-10-28T10:28:08Z
+  name: ebs-loss
+  version: 0.1.0
+  annotations:
+    categories: Kubernetes
+    vendor: CNCF
+    support: https://slack.kubernetes.io/
+spec:
+  displayName: ebs-loss
+  categoryDescription: |
+    EBS Loss contains chaos to disrupt state of infra resources. The experiment can induce ebs volume loss against specified application. 
+    - Causes ebs volume loss from node or ec2 instance for a certain chaos duration
+    - Causes Pod to get Evicted if the Pod exceeds it Ephemeral Storage Limit.
+    - Tests deployment sanity (replica availability & uninterrupted service) and recovery workflows of the application pod
+  keywords:
+    - Kubernetes
+    - EBS
+    - Volume
+    - State 
+  platforms:
+    - AWS
+  maturity: alpha
+  chaosType: infra
+  maintainers:
+    - name: Udit Gaurav
+      email: uditgaurav@mayadata.io
+  provider:
+    name: Mayadata
+  labels:
+    app.kubernetes.io/component: chartserviceversion
+    app.kubernetes.io/version: latest
+  links:
+    - name: Source Code
+      url: https://github.com/litmuschaos/litmus-go/tree/master/experiments/kube-aws/ebs-loss
+    - name: Documentation
+      url: https://docs.litmuschaos.io/docs/ebs-loss/
+    - name: Video
+      url:
+  icon:
+    - url: 
+      mediatype: ""
+  chaosexpcrdlink: https://raw.githubusercontent.com/litmuschaos/chaos-charts/master/charts/kube-aws/ebs-loss/experiment.yaml
diff --git a/charts/kube-aws/ebs-loss/engine.yaml b/charts/kube-aws/ebs-loss/engine.yaml
new file mode 100644
index 0000000..182d565
--- /dev/null
+++ b/charts/kube-aws/ebs-loss/engine.yaml
@@ -0,0 +1,36 @@
+apiVersion: litmuschaos.io/v1alpha1
+kind: ChaosEngine
+metadata:
+  name: nginx-chaos
+  namespace: default
+spec:
+  annotationCheck: 'false'
+  engineState: 'active'
+  chaosServiceAccount: ebs-loss-sa
+  monitoring: false
+  # It can be retain/delete
+  jobCleanUpPolicy: 'delete'
+  experiments:
+    - name: ebs-loss
+      spec:
+        components:
+          env: 
+            # set chaos duration (in sec) as desired
+            - name: TOTAL_CHAOS_DURATION
+              value: '60'
+
+            # Instance ID of the target ec2 instance 
+            - name: EC2_INSTANCE_ID
+              value: ''
+
+            # provide EBS volume id attached to the given instance
+            - name: EBS_VOL_ID
+              value: ''              
+
+            # Enter the device name which you wanted to mount only for AWS.   
+            - name: DEVICE_NAME
+              value: '/dev/sdb'
+              
+            # provide the region name of the instace
+            - name: REGION
+              value: ''
\ No newline at end of file
diff --git a/charts/kube-aws/ebs-loss/experiment.yaml b/charts/kube-aws/ebs-loss/experiment.yaml
new file mode 100644
index 0000000..b83b512
--- /dev/null
+++ b/charts/kube-aws/ebs-loss/experiment.yaml
@@ -0,0 +1,76 @@
+apiVersion: litmuschaos.io/v1alpha1
+description:
+  message: |
+    Detaching an ebs volume from ec2 instance.
+kind: ChaosExperiment
+metadata:
+  name: ebs-loss
+  labels:
+    name: ebs-loss
+    app.kubernetes.io/part-of: litmus
+    app.kubernetes.io/component: chaosexperiment
+    app.kubernetes.io/version: latest
+spec:
+  definition:
+    scope: Cluster
+    permissions:
+      - apiGroups:
+          - ""
+          - "batch"
+          - "litmuschaos.io"
+        resources:
+          - "jobs"
+          - "pods"
+          - "events"
+          - "pods/log"
+          - "secrets"
+          - "chaosengines"
+          - "chaosexperiments"
+          - "chaosresults"
+        verbs:
+          - "create"
+          - "list"
+          - "get"
+          - "patch"
+          - "update"
+          - "delete"
+    image: "litmuschaos/go-runner:latest"
+    imagePullPolicy: Always
+    args:
+    - -c
+    - ./experiments -name ebs-loss
+    command:
+    - /bin/bash
+    env:
+    - name: TOTAL_CHAOS_DURATION
+      value: '60'
+
+    # Period to wait before and after injection of chaos in sec
+    - name: RAMP_TIME
+      value: ''
+
+    - name: EC2_INSTANCE_ID
+      value: ''
+
+    - name: EBS_VOL_ID
+      value: ''
+
+    - name: REGION
+      value: ''
+
+    # provide the LIB
+    # only litmus supported
+    - name: LIB
+      value: 'litmus'  
+          
+    - name: DEVICE_NAME
+      value: '' 
+          
+    labels:
+      name: ebs-loss
+      app.kubernetes.io/part-of: litmus
+      app.kubernetes.io/component: experiment-job
+      app.kubernetes.io/version: latest
+    secrets:
+    - name: cloud-secret
+      mountPath: /tmp/
diff --git a/charts/kube-aws/ebs-loss/rbac.yaml b/charts/kube-aws/ebs-loss/rbac.yaml
new file mode 100644
index 0000000..b8aaf57
--- /dev/null
+++ b/charts/kube-aws/ebs-loss/rbac.yaml
@@ -0,0 +1,37 @@
+---
+apiVersion: v1
+kind: ServiceAccount
+metadata:
+  name: ebs-loss-sa
+  namespace: default
+  labels:
+    name: ebs-loss-sa
+    app.kubernetes.io/part-of: litmus
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRole
+metadata:
+  name: ebs-loss-sa
+  labels:
+    name: ebs-loss-sa
+    app.kubernetes.io/part-of: litmus
+rules:
+- apiGroups: ["","litmuschaos.io","batch"]
+  resources: ["pods","jobs","secrets","events","pods/log","chaosengines","chaosexperiments","chaosresults"]
+  verbs: ["create","list","get","patch","update","delete"]
+---
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+  name: ebs-loss-sa
+  labels:
+    name: ebs-loss-sa
+    app.kubernetes.io/part-of: litmus
+roleRef:
+  apiGroup: rbac.authorization.k8s.io
+  kind: ClusterRole
+  name: ebs-loss-sa
+subjects:
+- kind: ServiceAccount
+  name: ebs-loss-sa
+  namespace: default
diff --git a/charts/kube-aws/icons/ebs-loss.png b/charts/kube-aws/icons/ebs-loss.png
new file mode 100644
index 0000000..fd09e34
Binary files /dev/null and b/charts/kube-aws/icons/ebs-loss.png differ
diff --git a/charts/kube-aws/kube-aws.chartserviceversion.yaml b/charts/kube-aws/kube-aws.chartserviceversion.yaml
index dc9cf22..294b162 100644
--- a/charts/kube-aws/kube-aws.chartserviceversion.yaml
+++ b/charts/kube-aws/kube-aws.chartserviceversion.yaml
@@ -13,6 +13,7 @@ spec:
     kube-aws contains chaos to disrupt state of aws resources running part of kubernetes cluster
   experiments:
     - k8-aws-ec2-terminate
+    - ebs-loss
   keywords:
     - AWS
     - EC2
@@ -20,7 +21,6 @@ spec:
   maintainers:
     - name: sumit
       email: sumit_nagal@intuit.com
-  minKubeVersion: 1.12.0
   provider:
     name: Intuit
   links:
diff --git a/charts/kube-aws/kube-aws.package.yaml b/charts/kube-aws/kube-aws.package.yaml
index da95174..4ed388b 100644
--- a/charts/kube-aws/kube-aws.package.yaml
+++ b/charts/kube-aws/kube-aws.package.yaml
@@ -3,4 +3,8 @@ experiments:
   - name: k8-aws-ec2-terminate 
     CSV: k8-aws-ec2-terminate.chartserviceversion.yaml
     desc: "k8-aws-ec2-terminate"
+  - name: ebs-loss 
+    CSV: ebs-loss.chartserviceversion.yaml
+    desc: "ebs-loss"
+