Questions tagged [aws-fis]

AWS Fault Injection Simulator is a fully managed service for running fault injection experiments on AWS that makes it easier to improve an application’s performance, observability, and resiliency.

Fault injection experiments are used in chaos engineering, which is the practice of stressing an application in testing or production environments by creating disruptive events, such as sudden increase in CPU or memory consumption, observing how the system responds, and implementing improvements. Fault injection experiment helps teams create the real-world conditions needed to uncover the hidden bugs, monitoring blind spots, and performance bottlenecks that are difficult to find in distributed systems.

5 questions
3
votes
2 answers

Where to find AWS Systems Manager (SSM) Document ARNs?

I am wanting to run an SSM Document on my EC2 instance, AWSFIS-Run-CPU-Stress. It is being executed via AWS Fault Injection Simulator (FIS), which requires a documentARN to be specified, specifically in…
x3nr0s
  • 1,946
  • 4
  • 26
  • 46
2
votes
0 answers

AWS FIS Memory stress not stressing beyond 5-6%

I have been trying to use FIS to stress cpu and memory using ssm commands and watch the results using 'top' command in ubuntu. While cpu stress command pushes the cpu to 99.9%, the memory stress command (AWSFIS-Run-Memory-Stress) doesn't push %MEM…
mgn
  • 129
  • 1
  • 10
1
vote
1 answer

Unable to start AWSFIS-Run-CPU-Stress

While running AWSFIS-Run-CPU-Stress i am getting below error: Unable to start action, due to a platform mismatch between the specified document and the targeted instances. I am trying this in Windows EC2 instance My Experiment script look like…
Sameer
  • 35
  • 1
  • 11
1
vote
2 answers

AWS Fault Injection Simulator returning 'Not authorized to perform the required action.'

I am trying to use AWS FIS to stress CPU on an ubuntu VM thru ssm send command (aws:ssm:send-command/AWSFIS-Run-CPU-Stress). When I ssh to the VM and use 'top' command I see the CPU shooting up successfully from 0.3% to 99.9% but surprisingly the…
mgn
  • 129
  • 1
  • 10
0
votes
0 answers

Karpenter - half of nodes state are not ready after simulate spot disruption with aws fis

I have an EKS cluster running with Karpenter provisioning. Everything worked as expected, but when I used AWS FIS to simulate spot instances interruption, I faced a weird behavior - new nodes provisioned, but half of the new nodes were stuck in not…