AWS Weekly Roundup: GPT-6 Sol and Luna, Claude Opus 5.5 on Amazon Bedrock, Strands harness, and more (September 28, 2026)

CloudWatch Omni, enhanced EventBridge custom event buses, the SageMaker HyperPod Inference Gateway with GPU-aware routing, and AI agent skills for SES and End User Messaging — plus new frontier models.

Introducing enhanced custom event buses in Amazon EventBridge

EventBridge now offers an enhanced custom event bus purpose-built for organizations scaling event-driven applications across teams and accounts. Instead of the classic bus-per-team topology with bus-to-bus routing, you deploy a single centralized bus shared across every account in your organization.

What's new

• Organization-wide sharing through AWS RAM — one shared bus serves every team. Publishers send events, subscribers consume only what they need, and EventBridge handles ordering, retention, routing, and delivery. Share with an account, an organization, an organizational unit, or an IAM role/user — without setting up cross-account permissions or bus-to-bus routing yourself.
• Optional event ordering — sequenced delivery for workloads that need it.
• A simplified Subscriber resource that bundles filtering, targets, and retries in one object.
• Content-based deduplication — drop duplicate events without bespoke logic.
• Synchronous invocation for targets like AWS Lambda.

The economics change too

A new ingress/egress pricing model replaces the compounding cross-account routing charges of multi-bus setups — cost grows with events actually handled, not with hops between buses. Existing buses keep working unchanged as "classic," so moving to the enhanced bus is additive, not a forced migration.

Getting started

In the EventBridge console, choose Custom event bus on the create page — the recommended new option with ordered delivery, filter patterns, event replay, and sharing across your AWS organization. "Custom event bus – classic" remains available for existing workloads. Enable sharing within your organization (AWS RAM handles the mechanics), pick a principal type, and teams across accounts can publish and subscribe on the same bus immediately.

Bottom line

For organizations where event-driven sprawl has produced a web of buses, rules, and compounding cross-account routing costs, the enhanced custom event bus is the consolidation play: one bus, AWS-managed ordering and delivery, one billing model. If your event architecture is outgrowing the classic multi-bus pattern, this is worth evaluating now.