Amazon ECS now supports network fault injection experiments on AWS Fargate

Amazon Elastic Container Services (Amazon ECS) now allows you to perform network fault injection experiments on your applications deployed on AWS Fargate. Fault injection experiments create disruptions to test how your applications behave, helping you improve application performance, observability, and resilience. AWS Fault Injection Service (AWS FIS) now supports 6 actions for ECS on both EC2 and Fargate: network latency, network blackhole, network packet loss, CPU stress, I/O stress, and kill process.

Developers and operators can now verify the response of their application to potential network errors, some of which may also be required for regulatory compliance. By reproducing network behaviors that may cause applications to fail, you can identify gaps in application configurations, monitoring, alarms, and operational response. Amazon ECS is introducing the ability to opt-in to allow tasks to use a fault injector such as AWS FIS to perform network experiments for increasing network latency, increasing packet loss, and blackhole port testing (dropping inbound or outbound traffic) to test how your applications perform, in addition to existing resource stress experiments.

The new experience is now automatically enabled in all AWS Regions and integration with the AWS Fault Injection Service in those regions where AWS FIS is available.

For more details, go to Amazon ECS fault Injection documentation and the AWS FIS user guide.