{
  "_comment": "Skeleton AWS FIS experiment template for an AZ power-interruption-style test, with a CloudWatch alarm stop condition and tag-scoped targets. This is a STARTING POINT illustrating the safety wiring (stopConditions + tag targeting), not a drop-in template. Prefer the managed 'AZ Availability: Power Interruption' scenario from the FIS Scenario Library for the full multi-service symptom set. Replace ACCOUNT, REGION, ROLE, ALARM, and tag values. Run in a NON-PROD account first.",
  "description": "AZ impairment rehearsal - stop EC2 in one AZ, scoped by tag, halted on SLO breach",
  "roleArn": "arn:aws:iam::ACCOUNT:role/fis-experiment-role",
  "stopConditions": [
    {
      "source": "aws:cloudwatch:alarm",
      "value": "arn:aws:cloudwatch:REGION:ACCOUNT:alarm:steady-state-slo-breach"
    }
  ],
  "targets": {
    "ChaosEligibleInstances": {
      "resourceType": "aws:ec2:instance",
      "selectionMode": "ALL",
      "resourceTags": {
        "chaos-eligible": "true",
        "az-impact-group": "az-a"
      },
      "filters": [
        {
          "path": "State.Name",
          "values": ["running"]
        },
        {
          "path": "Placement.AvailabilityZone",
          "values": ["REGION-a"]
        }
      ]
    }
  },
  "actions": {
    "StopInstancesInAZ": {
      "actionId": "aws:ec2:stop-instances",
      "description": "Simulate compute loss in one AZ; multi-AZ design should ride through",
      "parameters": {
        "startInstancesAfterDuration": "PT30M"
      },
      "targets": {
        "Instances": "ChaosEligibleInstances"
      }
    }
  },
  "tags": {
    "Name": "az-power-interruption-rehearsal",
    "environment": "non-prod"
  }
}