channel
AWS Default Event Bus
The account's built-in EventBridge bus, used only for AWS-generated service events (S3, RDS, Bedrock, ECS).
Channel
Overview
Some RIO rules listen on the account’s built-in default bus rather than on
the RIO Events Bus. This is because AWS
services always publish their own events to default — they cannot be redirected to a custom bus.
These are AWS-managed events, so the RIO naming rules in .claude/rules/eventbridge.md do not
apply to them; they keep AWS’s own structure.
Rules on this bus
source | detail-type | Consumer | Declared in |
|---|---|---|---|
aws.s3 | Object Created | CRM data-sync state machine, for product-master file uploads | rio-ingestion-service/infrastructure/modules/ecs/crm-data-sync.yaml:368-390 |
aws.rds | RDS DB Instance Event | Lambda that re-registers the RDS IP in a target group | rio-infra/infrastructure/template.yaml:401-419 |
aws.bedrock | Batch Inference Job State Change | Batch assembler, for LLM distillation jobs | rio-deal-desk/infrastructure/distillation/template.yaml:766-782 |
aws.ecs | (all ECS detail-types) | CloudWatch Logs, 7-day retention | rio-infra/infrastructure/template.yaml:361-372 |
Event-driven architecture documentation: RIO