Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Change EC2 Instance State

Attack

Attack

Reboot, terminate, stop or hibernate EC2 instances
Install now

Change EC2 Instance State

Reboot, terminate, stop or hibernate EC2 instances
Attack

Attack

Install now

Change EC2 Instance State

Attack

Attack

Reboot, terminate, stop or hibernate EC2 instances
Install now

Change EC2 Instance State

Reboot, terminate, stop or hibernate EC2 instances
Attack

Attack

Install now
Go back to list

Introduction

This action leverages AWS EC2 API to manipulate the state of EC2 instances. More specifically, it can reboot, stop, hibernate and terminate them.

Use Cases

  • Verify auto-scaling of a Kubernetes node group.
  • Understand how pods are shifted across different nodes within a Kubernetes cluster.
  • Verify that system services come up on system start.
  • Check that your monitoring solution informs you about this occurrence.

Rollback

Note that this attack does not support any rollback. The attack only transmits the API call, e.g., StopInstances or TerminateInstances.

Parameters

ParameterDescriptionDefault
ActionHow the EC2 instance state should be changed. Reboot, stop, hibernate, terminate.
Statistics
-Stars
Tags
AWS
AWS EC2
Cloud
Homepage
hub.steadybit.com/extension/com.steadybit.extension_aws
License
MIT
MaintainerSteadybit
Install now

Useful Templates

See all
Load balancer covers an AWS EC2 restart

EC2 is part of the AWS Elastic Compute Cloud, which acquires and releases resources depending on the traffic demand. Check whether your application is elastic as well by rebooting an EC2 instance.

Motivation

Depending on your traffic demand, you can use AWS cloud's ability to acquire and release resources automatically. Some services, such as S3 and SQS, do that automatically, while others, such as EC2, integrate with AWS Auto Scaling. Once configured, it boils down to fluctuating EC2 instances starting or shutting down frequently. Even when not using AWS Autoscaling, your EC2 instances may need to be restarted occasionally for maintenance and updating purposes. Thus, it is best practice to validate your application's behavior.

Structure

We ensure that a load-balanced user-facing endpoint fully works while having all EC2 instances available. While restarting an EC2 instance, the HTTP endpoint continues operating but may suffer from degraded performance (e.g., lower success rate or higher response time). The performance should recover to a 100% success rate once all EC2 instances are back.

Solution Sketch

  • AWS Well-Architected Framework
  • Kubernetes liveness, readiness, and startup probes
Scalability
Redundancy
Elasticity
AWS

EC2-instances

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!

Steadybit logoResilience Hub
Try Steadybit
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon