Skip to content

Latest commit

 

History

History
42 lines (33 loc) · 1.45 KB

File metadata and controls

42 lines (33 loc) · 1.45 KB

Unit 003: Hermes The Bureaucrat - Subunit 003: EventBridge Integration

Objective

Configure EventBridge target to route all events to Hermes Lambda for logging.

Key Technical Decisions

EventBridge Target Configuration

  • Rule: coderipple-hermes-all-events (already created in Unit 002)
  • Target: Hermes Lambda function
  • Input: Full event payload (no transformation)
  • Retry Policy: 3 attempts with exponential backoff

Lambda Trigger Setup

  • Event Source: EventBridge custom bus coderipple-events
  • Event Pattern: All events from coderipple.system
  • Batch Size: 1 (process events individually)
  • Maximum Age: 1 hour (discard old events)

Error Handling

  • Dead Letter Queue: SQS queue for failed Lambda invocations
  • CloudWatch Alarms: Monitor failed invocations
  • Retry Logic: Built-in EventBridge retry with backoff

IAM Permissions

  • EventBridge permission to invoke Hermes Lambda
  • Lambda execution role with EventBridge receive permissions
  • Cross-service IAM trust relationships

Testing Strategy

  • Send test events through Telephonist
  • Verify Hermes receives and processes events
  • Check log entries appear in Cabinet S3 bucket
  • Validate public read access to logs

Dependencies

  • Hermes Lambda function (Subunit 001)
  • Cabinet S3 bucket (Subunit 002)
  • EventBridge Telephonist (Unit 002 - Complete)

Status: Planning Complete

Ready for EventBridge target configuration and end-to-end testing.