Scaling AWS Fault Injection Service across your organization using Account Controls

This article discusses scaling AWS Fault Injection Service (FIS) across an organization using account controls and Service Control Policies (SCPs). Key points include:

• Chaos engineering helps verify system resilience by injecting controlled failures
• Organizations can use SCPs and IAM permissions to enable FIS experiments safely
• Two key roles are recommended:
  • AWS-FIS-Experiment-Orchestrator: Creates and manages experiment templates
  • AWS-FIS-Experiment-Executor: Executes fault injection actions
• SCPs act as guardrails to prevent unauthorized network changes
• Standardizing FIS roles helps organizations adopt chaos engineering securely

The approach enables controlled network fault experiments while maintaining organizational security and network integrity.