Asset Notification Fan-out

Asset Notification Fan-out A data-flow diagram generated by Archify. 01 / Outcome 02 / Routing 03 / Fan-out 04 / Subscribers 05 / Recovery Step Functions · records terminal state · 01 / Outcome · producer Step Functions records terminal state producer EventBridge · asset lifecycle bus · 02 / Routing · route facts EventBridge asset lifecycle bus route facts Notification Rule · ready · rejected · failed · 02 / Routing · event pattern Notification Rule ready · rejected · failed event pattern SNS Standard Topic · asset notifications · 03 / Fan-out · fan-out SNS Standard Topic asset notifications fan-out Integration Queue · durable machine consumer · 04 / Subscribers · raw delivery Integration Queue durable machine consumer raw delivery Operator Email · confirmed subscription · 04 / Subscribers · human channel Operator Email confirmed subscription human channel Rule-target DLQ · EventBridge → SNS · 03 / Fan-out · 14 days Rule-target DLQ EventBridge → SNS 14 days SQS Delivery DLQ · SNS → SQS failures · 05 / Recovery · 14 days SQS Delivery DLQ SNS → SQS failures 14 days Email Delivery DLQ · SNS → email failures · 05 / Recovery · 14 days Email Delivery DLQ SNS → email failures 14 days Asset State Changed schema v1 match lifecycle event EventBridge rule publish event at-least-once push raw event SQS subscription rejected · failed filtered email subscription topic publish failed target delivery SQS delivery exhausted subscription redrive email delivery exhausted subscription redrive Legend primary data policy / PII data flow

Service Boundaries

  • • EventBridge decides which facts enter the channel
  • • SNS copies each publication to every subscription
  • • SQS retains work until a consumer is ready

Independent Subscribers

  • • The integration queue receives the original event body
  • • Email is optional and requires recipient confirmation
  • • Adding a subscriber does not change the workflow

Failure Ownership

  • • Each subscription owns its delivery failures
  • • A future queue consumer will own processing redrive
  • • Operators inspect retained messages before replay