Home icon

Best practices for utilizing AWS Systems Manager with AWS Fault Injection Service

AWS Cloud Operations Blog



This article discusses best practices for utilizing AWS Systems Manager (SSM) with AWS Fault Injection Service (FIS) to improve application resilience and reliability through chaos engineering experiments.

  • FIS allows performing fault injection experiments to stress test applications and uncover potential issues
  • SSM Run Command enables executing scripts across different systems and platforms
  • Key best practices for SSM documents include:
    • Modular document structure
    • Clear parameter definitions
    • OS detection
    • Implementing preconditions
  • Code best practices involve:
    • Idempotency
    • Proper timeouts
    • Comprehensive logging
    • Thorough cleanup procedures
    • Service state restoration

The goal is to create robust chaos engineering experiments that improve application resilience by systematically testing system responses to disruptive events.



Go to article

The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.

Related articles

Jun 23
2025
Simulating partial failures with AWS Fault Injection Service
Jul 31
2025
Learn from AWS Fault Injection Service team’s approach to Game Days
Sep 3
2024
AWS Fault Injection Service introduces additional safety control
Apr 12
2025
Scaling AWS Fault Injection Service across your organization and accounts

The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.