> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Demo Run Experiment Pod Delete on EKS
> Learn to execute a pod-deletion experiment on Amazon EKS using AWS FIS to validate Kubernetes pod replacement without user disruption.
In this guide, you’ll learn how to execute a pod-deletion experiment on Amazon EKS using AWS FIS. We’ll walk through:
1. Selecting the built-in EKS pod-delete scenario
2. Creating and configuring an experiment template
3. Launching the experiment
4. Monitoring pod replacement and service continuity
This approach helps you validate your Kubernetes Deployment or ReplicaSet automatically replaces pods without user-facing disruption.
***
## Prerequisites
Before you begin, ensure:
* You have an existing Amazon EKS cluster named `pet-site`.
* The IAM role you’ll assign to FIS (e.g., `EKS-FIS-Role`) has permissions to delete pods and write logs.
* CloudWatch Logs group (e.g., `FISExperiments`) is either created or will be created by FIS.
| IAM Permission | Purpose |
| ---------------------------- | ------------------------------------- |
| fis:CreateExperimentTemplate | Create FIS experiment templates |
| fis:StartExperiment | Launch experiments |
| eks:DeletePods | Delete pods in the target EKS cluster |
| logs:CreateLogGroup | Create CloudWatch Logs groups |
| logs:PutLogEvents | Publish experiment logs |
Make sure your IAM role trusts the `fis.amazonaws.com` service principal. For more details, see [AWS FIS IAM permissions](https://docs.aws.amazon.com/fis/latest/userguide/security_iam_id-based-policy-examples.html).
***
## 1. Navigate to Fault Injection Service
1. Open the AWS Management Console.
2. Go to **AWS Resilience Hub** → **Fault Injection Service**.
3. Click **Experiment templates** in the sidebar.
***
## 2. Select the EKS Pod Delete Scenario
1. Under **Scenario library**, search for **EKS Stress: Pod Delete**.
2. Click **Create experiment template**.
FIS immediately populates the template’s name, description, actions, and targets based on the built-in scenario.
***
## 3. Configure the Target
By default, the scenario target is set to delete pods in your cluster. Verify or update:
* **Resource type**: `eks:pod`
* **Cluster**: `pet-site`
* **Label selector**: `app=pet-site`
Ensure these match your Deployment labels so FIS deletes only the intended pods.
Review the auto-generated actions and targets:
***
## 4. Select IAM Role and Logging
1. Under **Service role**, choose your FIS execution role (`EKS-FIS-Role`).
2. For **Experiment logging**, select the CloudWatch Logs group (`FISExperiments`) or create one on the fly.
***
## 5. Define the Hypothesis
> **Hypothesis:** When FIS deletes a `pet-site` pod, the Kubernetes control plane immediately spins up a replacement pod. Service latency and availability remain within SLAs.
Validate this by monitoring your Deployment or ReplicaSet’s desired vs. actual pod counts.
***
## 6. Start and Monitor the Experiment
1. Click **Start experiment**.
2. Watch the experiment lifecycle transition from **Initiating** → **Running** → **Completed**.
3. Use the FIS dashboard and CloudWatch metrics (e.g., `kube_deployment_status_replicas_available`) to confirm a new pod appears within seconds.
Run FIS experiments only in non-production or controlled environments. Always validate on staging clusters before production.
### AWS CLI Shortcut
After creating the template, you can start the experiment via CLI:
```bash theme={null}
aws fis start-experiment \
--experiment-template-id
```
***
## Links and References
* [AWS Fault Injection Simulator User Guide](https://docs.aws.amazon.com/fis/latest/userguide/)
* [Amazon EKS Documentation](https://docs.aws.amazon.com/eks/latest/userguide/)
* [Kubernetes ReplicaSet Concepts](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/)
* [CloudWatch Logs Developer Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/)