AWS Fault Injection Service
Managed chaos experiments run on demand from a template of actions, targets and stop conditions.
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| accelerator | enum | none | gpu | asic | no | none | inherited |
| actionMode | enum | sequential | parallel | no | — | inherited |
| concurrency | integer | — | no | — | inherited |
| fanoutStrategy | enum | none | push | pull | hybrid | no | none | inherited |
| fanoutThreshold | integer | — | no | — | inherited |
| idempotent | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| multiAccount | boolean | — | no | false | inherited |
| rateControl | enum | none | fixed | aimd | no | none | inherited |
| schedule | string | — | no | — | inherited |
| stopConditions | boolean | — | no | — | inherited |
| trigger | enum | queue | stream | schedule | batch | manual | yes | — | ▸ manual |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
Pure push fan-out over a social graph is brutal at the tail: one post from an account with millions of followers becomes millions of cache writes. A follower threshold above which readers merge at read time bounds that write amplification.
- — all of these hold:
- — the node's `fanoutStrategy` is "push"
- — the node's `fanoutThreshold` has no value
- — the design contains a node of kind graph-database
One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.
- — all of these hold:
- — the node has more than 1 incoming edge from a queue
- — the design requirement `isolation.perQueue` is true
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "fis", component: "aws-fis" }# yaml-language-server: $schema=../../schema/component.schema.json # AWS Fault Injection Service: managed chaos experiments run from an experiment template of actions and # targets. Per "What is AWS Fault Injection Service?" experiments are started on demand, actions run # sequentially or in parallel, and targets are in the experiment's own account unless multi-account is used. schemaVersion: "1" type: "component" id: "aws-fis" kind: "worker" provider: "aws" docs: "https://docs.aws.amazon.com/fis/latest/userguide/what-is.html" defaults: trigger: "manual" managed: true properties: stopConditions: type: "boolean" actionMode: type: "enum" values: ["sequential", "parallel"] multiAccount: type: "boolean" default: false