AWS EventBridge integration

Configure an event bus

Choose a commercial AWS region and existing bus name, source (for example struct.telemetry), and detail type. Event detail contains the configured JSON envelope. Configure scoped access/session credentials. The adapter checks bus existence and validates each PutEvents entry; an HTTP 200 with FailedEntryCount is not delivery success. A concurrent deletion after the existence check remains a provider-side race; acceptance does not prove rule or subscriber processing.

EventBridge rules can forward accepted events into your existing infrastructure. Struct does not create buses, rules, Lambda functions or paid resources. One entry is published per attempt.

Least privilege

DescribeEventBus is used to avoid silently publishing to an absent bus; PutEvents permits publication. Scope both to the selected bus and optionally restrict event source/detail type through AWS policy conditions.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "events:PutEvents",
        "events:DescribeEventBus"
      ],
      "Resource": "arn:aws:events:us-east-1:123456789012:event-bus/telemetry"
    }
  ]
}

Troubleshooting

Check region, bus existence, IAM resource policy, source and detail type. Per-entry throttling retries; per-entry permission/validation failures become terminal. Correct configuration, then recover eligible original deliveries from Delivery; replay does not route events to newly added destinations.