![]() ![]() Configurable parameters include: the duration of the action, target CPU load percentage, and the number of CPU stressors. ![]() The complete list of new actions is listed in the following table: Action IdentifierĪdds CPU stress to one or more Pods. ![]() Pods can also be terminated to evaluate application resiliency. There are a variety of network failures that can be injected, including adding latency to network traffic and dropping all or a percentage of network packets. With the new actions, you can evaluate how your application performs under load by applying CPU, memory, or I/O stress to targeted Pods and containers. The new EKS Pod actions give you specific control to inject faults into EKS Pods without requiring installation of any agents, extra libraries, or orchestration software. New FIS EKS Pod actionsįIS has added seven new fault injection actions that target EKS Pods. In addition to individual AWS services, FIS also injects Amazon EC2 control plane level faults (e.g., API errors and API throttling) to test a wide array of failure scenarios to build confidence in the reliability of your application. This includes stopping Amazon Elastic Compute Cloud (Amazon EC2) instances, adding latency to network traffic and pausing I/O operations on Amazon Elastic Block Store (Amazon EBS) volumes.įIS supports a range of AWS services including Amazon EKS. FIS gives you the ability to inject faults into the underlying compute, network, and storage resources. AWS Fault Injection SimulatorĪWS FIS is a fully managed service for running chaos engineering experiments to test and verify the resilience of your applications. In this blog, we demonstrate how to automate running chaos engineering experiments using the new features in AWS Fault Injection Simulator (AWS FIS) to target Amazon Elastic Kubernetes Service (Amazon EKS) Pods. Chaos engineering is the discipline of verifying the resilience of your application architecture to identify unforeseen risks, address weaknesses, and ultimately improve confidence in the reliability of your application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |