Stress the CPU of an ECS task.
This attack will run the AWSFIS-Run-CPU-Stress SSM Document on the target ECS task using the SSM agent.
Test the behavior of the ECS task when the CPU is under high load.
execute-command
The issued SSM command running on the SSM agent will be cancelled and the cpu stress will be stopped.
Useful Templates
Validate your observability to detect a CPU spike in your AWS ECS cluster
When you have New Relic configured to detect CPU spikes in your AWS ECS cluster, you can easily validate your observability strategy with this experiment template.
First, we validate whether New Relic has no ongoing incident. After that, we inject the CPU spike for an ECS service and expected that New Relic detect this as an incident within the given time frame of 3 minutes.
Verify that your ECS service is scaled up on increased CPU usage.
Important ECS services should be scaled up within a reasonable time for an elastic and resilient cloud infrastructure. Undetected high CPU spikes and long startup times are undesirable in these infrastructures.
First, we ensure that all ECS service's tasks are ready to serve traffic. Afterward, we inject high CPU usage into the ECS task and expect that within a reasonable amount of time, ECS increases the number of ECS tasks and they become ready to handle incoming traffic.
More ECS Task Actions
Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!
No worries, our reliability experts are here to help: book a demo with them!
AttackAttack
AttackAttack
Go back to list
AttackAttack