Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Stress CPU

AttackAttack
Stresses CPU for the given duration
Targets:
ECS Tasks
Install now

Stress CPU

Stresses CPU for the given duration
AttackAttack
Targets:
ECS Tasks
Install now

Stress CPU

AttackAttack
Stresses CPU for the given duration
Targets:
ECS Tasks
Install now

Stress CPU

Stresses CPU for the given duration
AttackAttack
Targets:
ECS Tasks
Install now
Go back to list

Introduction

Stress the CPU of an ECS task.

Details

This attack will run the AWSFIS-Run-CPU-Stress SSM Document on the target ECS task using the SSM agent.

Use Cases

Test the behavior of the ECS task when the CPU is under high load.

  • Will the application crash? Does it recover from the high load?
  • Does the auto-scaling work as expected?
  • Does the load balancing care for busy workers?
  • Is your alerting properly configured?

Prerequisites

Rollback

The issued SSM command running on the SSM agent will be cancelled and the cpu stress will be stopped.

Parameters

ParameterDescriptionDefault
Load on Container CPUHow much CPU load should be inflicted?100%
Container CPUsHow many workers should be used to stress the CPU?1 per core
DurationHow long should the CPU be stressed?30s

Useful Templates

See all
New Relic detects an incident for CPU spikes in an ECS task

Validate your observability to detect a CPU spike in your AWS ECS cluster

Motivation

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.

Structure

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.

New Relic
AWS ECS
CPU
ECS Tasks
New Relic Accounts
AWS ECS Service Is Scaled up Within Reasonable Time

Verify that your ECS service is scaled up on increased CPU usage.

Motivation

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.

Structure

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.

Scalability
CPU
AWS ECS
AWS
ECS Services
ECS Tasks

More ECS Task Actions

See all
Start Using Steadybit Today

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!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Statistics
-Stars
Tags
AWS
AWS ECS
Cloud
CPU
Homepage
hub.steadybit.com/extension/com.steadybit.extension_aws
License
MIT
MaintainerSteadybit
Install now
Steadybit logoResilience Hub
Try Steadybit
© 2025 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon