Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTo route events between EventBridge buses in different AWS accounts, authorize the sender on the destination bus, then create a rule on the source bus that selects the events to forward and targets the destination bus ARN. The source rule needs an IAM role allowed to call events:PutEvents on that destination. On the receiving bus, create rules that match the events and explicitly scope them to approved sender account IDs. This is the core of how to route events between EventBridge buses across AWS accounts.
The arrangement has two independent filtering decisions: the source rule decides what leaves the sender, and each destination rule decides what happens after arrival. Treat the account boundary as a security boundary, not simply as another target configuration. Account IDs, bus policies, IAM permissions, Region support, and destination-side patterns all have to agree.
As an Amazon Associate I earn from qualifying purchases.
How cross-account bus routing works
The route has two distinct authorization checks. The sending account’s rule uses an IAM role to put events onto the receiving bus, while the receiving bus has a resource-based policy that permits the intended sender. A rule on the source bus determines which events are sent; separate rules on the destination bus determine what happens to events after they arrive.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →In practice, the flow is: source event bus → source rule and target role → destination event bus → destination rules. The target is the destination bus ARN, which identifies the bus and its account and Region. Cross-account access is not enabled merely by knowing that ARN: both sides of the authorization relationship must be configured.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
EventBridge’s default bus can receive events from AWS services, authorized AWS accounts, and PutEvents calls. Cross-account access is granted through a resource-based policy on the receiving bus. See Amazon EventBridge’s cross-account sending and receiving guide and its reference on event bus permissions.
A useful way to troubleshoot the design is to keep the permissions and matching logic separate. A successful PutEvents authorization does not guarantee that a destination rule will match. Conversely, a perfectly written destination pattern cannot compensate for a missing source role or bus policy.
Plan the account and Region route
Before creating rules, identify the account ID, bus name, and Region on each side. Decide whether the destination is in the same Region or a different one, and check AWS’s current cross-Region support guidance for the specific Region pair. Cross-account routing can use buses in the same Region; cross-Region delivery is also available when the destination Region is supported. See AWS’s cross-Region event-routing guidance.
Write down the complete destination ARN before configuring the target. A typo in the account number, bus name, or Region can send the rule toward a resource that is not authorized, or simply toward the wrong environment. Distinguish development, staging, and production buses explicitly when several accounts use similar names.
| Planning choice | What to decide | Why it matters |
|---|---|---|
| Trust boundary | Authorize a specific sender account or an appropriately scoped AWS Organization. | The bus policy defines who can send events. A narrower grant limits the set of accounts that can reach the bus. |
| Routing scope | Choose the source event pattern and the destination bus for each rule. | The source rule controls which events cross the account boundary. |
| Region placement | Use the same Region or verify support for the cross-Region pair. | Cross-Region delivery is subject to supported-Region availability. |
| Cost ownership | Account for cross-account deliveries in the sending account. | AWS bills transferred cross-account events to the sender as custom events. |
| Operations | Plan how to manage roles, bus policies, rules, and delivery monitoring. | Each additional source or destination adds configuration and operational points to validate. |
For a single source and destination, the route is easy to map. At scale, make an inventory of every source rule, target role, destination bus policy, and receiving rule. This gives operators a way to identify which relationship should be changed when an account is added, removed, or moved to another Region.
Configure the destination bus policy
In the receiving account, attach a resource-based policy to the destination event bus. Grant permission to the intended sending account or, where appropriate, an AWS Organization. Keep the principal as narrow as your architecture allows, and use policy conditions where suitable. Event bus permissions can be constrained by account, organization, rule, or tags; consult AWS’s permissions reference for the policy options supported by your setup.
Choose the authorization scope deliberately. An account-level grant is easier to reason about when only one known account sends to the bus. An organization-level grant can suit a centrally managed multi-account environment, but it broadens the trust boundary to eligible accounts within that organization. Do not authorize every AWS account unless that is an intentional design and receiver-side rules are carefully scoped.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
The bus policy and the source rule’s IAM role serve different purposes: the bus policy is the receiving resource’s permission boundary, while the role supplies the sending rule’s permission to call events:PutEvents. Configure them so the intended sender is authorized under the selected policy design. AWS recommends using IAM roles for event bus targets generally.
Review policy conditions whenever the topology changes. A policy that was appropriate for one sender may be too broad after an organization-wide grant, while a policy narrowed to one account will block a newly approved account until it is updated. Keep the policy’s principal, conditions, and destination bus ARN aligned with the role attached to the source target.
Create the source rule, event pattern, and target role
- Select the source bus. In the sending account, choose the bus that receives the events you want to route.
- Define an event pattern. Match only the event types and details the destination account needs. A broad pattern forwards more traffic than necessary and makes the receiving boundary harder to manage.
- Set the destination. Add the destination event bus ARN as the rule’s target. Check the account ID, bus name, and Region in the ARN against the route plan.
- Attach an IAM role. The role used by the rule must allow
events:PutEventson the destination bus. The destination bus policy must also authorize the sender or role in a manner consistent with that role and your policy design. - Save and allow for activation. If you create the rule in the AWS console, the console can create the target role automatically. With CLI configuration, create and configure the role yourself. Allow a short period for a new or updated target to take effect.
A new cross-account event bus target created after March 2, 2023 must have an IAM role attached. This date applies to creation of the target; it does not mean that a role is optional for older targets as a general best practice. AWS recommends roles for event bus targets generally. Target behavior and configuration notes are in the event bus targets documentation.
Make the source pattern as selective as the business contract permits. For example, a rule intended to share order-status changes should not also forward unrelated account, billing, or infrastructure events simply because they use the same source bus. Selectivity limits the data crossing the account boundary, reduces unnecessary downstream matches, and makes cost estimates easier to understand.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Check the role’s trust and permission policies as a pair. The service must be able to assume the role, and the role must authorize events:PutEvents on the exact destination bus resource. A role with a broad action but an incorrect resource, or a correct resource but an unusable trust policy, will still fail delivery.
Create rules on the receiving bus
Arrival on the destination bus does not by itself decide which downstream action should run. Create destination-side rules whose event patterns match the incoming events and route them to the appropriate next action. In those patterns, include an account field listing the approved sender account ID or IDs.
This account check is especially important when the bus policy permits events from multiple accounts or an entire organization. AWS strongly recommends account scoping on every receiving-bus rule when the bus accepts events from all accounts, so a rule does not inadvertently match events from an unknown sender. For a rule intended to match events generated only in the receiver’s own account, specify the receiver account explicitly instead.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Do not assume that a pattern on the source rule is inherited by the destination. Recreate the relevant event-type and detail conditions on each receiving rule, then add the sender account condition. If several approved accounts send the same event contract, list those account IDs intentionally and review the list when ownership changes.
Recommended Free Tools
Validate delivery and troubleshoot the path
When an expected event does not reach its destination, check each boundary in order rather than changing the event pattern at random. Verify that the source rule matches the event, the target ARN identifies the intended bus, the target role has the destination permission, and the destination bus policy authorizes that sender. Then confirm that the Region pair is supported and that a receiving-bus rule matches the event, including its account scope.
- No events appear on the destination bus: inspect the source rule’s event pattern, target bus ARN, target role permission for
events:PutEvents, destination bus resource policy, and Region selection. - Events arrive but no destination action runs: check the receiving rule’s event pattern and its
accountfield. The destination rule is a separate match from the source forwarding rule. - A new or changed target appears inactive: allow a short period for the change to take effect, then recheck the target configuration and monitor delivery failures and service metrics in the deployment.
- A rule matches events from more senders than intended: narrow its event pattern and explicitly list approved sender account IDs. Review the destination bus policy as well.
- Only cross-Region routes fail: verify that the selected destination Region is currently supported for EventBridge cross-Region delivery; same-Region success does not prove that every Region pair is available.
- One environment works while another does not: compare the complete ARN, account IDs, policy principal, role permissions, event pattern, and Region rather than copying only the rule name.
Monitor delivery failures and relevant service metrics as part of operating the route; the EventBridge target documentation describes target behavior. The appropriate monitoring setup depends on the deployment, so confirm the metrics and failure-handling options applicable to the target and bus type you use.
Understand forwarding, billing, and bus-to-bus limits
A receiving account cannot relay the event to a third account through another bus rule
A receiver cannot take an event delivered cross-account and forward that received event onward to a third account by using another event bus rule. If multiple accounts need the event, plan delivery directly from the original sender or use another supported fan-out design rather than building a relay chain through the receiver.
This constraint affects the architecture plan for shared events. If accounts B and C both need an event originating in account A, model two source-to-destination relationships from A, with the required policies, roles, rules, and monitoring for each path. Do not assume that routing A → B and then adding B → C will create a supported distribution tree.
The sending account pays for transferred cross-account events
AWS classifies cross-account event bus deliveries as custom events billed to the sending account; AWS says the receiving account is not charged for those transferred events. The rate and regional details can change, so check the cross-account guide and live AWS pricing information before estimating a deployment. No rate is stated here because it depends on current pricing and Region.
Cost ownership should be part of the routing decision, especially when one producer fans out to several accounts or when a broad source pattern forwards high-volume traffic. Selective patterns reduce unnecessary transfers, but they do not change the need to account for every intended cross-account delivery in the sending account.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Do not rely on loop detection to make a routing cycle safe
AWS’s newer documentation for Custom Event Bus bus-to-bus delivery describes delivery roles, destination resource policies or AWS RAM sharing, and best-effort loop detection. Best-effort detection is not a reason to design a cycle or to depend on events passing through the same bus repeatedly. Confirm that the relevant Custom Event Bus feature set applies to your deployment, and design an acyclic route with deliberate source and destination rules. See AWS’s Custom Event Bus bus-to-bus guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a multi-account routing pattern
For a single sender and receiver, a source rule targeting one destination bus is usually the simplest arrangement to administer. At larger scale, compare the following trade-offs before multiplying rules and permissions:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Account-specific authorization: use when the sender set is known and should be individually approved. It creates a clear trust boundary, though more accounts may mean more policy administration.
- Organization authorization: consider when the accounts belong to a centrally managed organization and the intended trust boundary is organization membership. Scope event patterns and receiver rules to the business events and senders that should be processed.
- Direct routing from each origin: use when multiple downstream accounts need events, because the receiving account cannot relay cross-account events onward through another bus rule. Account for each source-to-destination relationship in policies, roles, rules, and monitoring.
- Same-Region versus cross-Region routing: choose the Region placement that fits the architecture, and verify support for cross-Region destinations before configuring the path.
There is no universal best layout independent of the trust boundary and number of destinations. Compare how many sender roles, destination bus policies, source rules, receiving rules, and monitoring points each option creates. Prefer a design whose permissions and event patterns make the intended flow easy to audit.
For centrally governed organizations, an organization-level permission can reduce repetitive policy edits, but it should be paired with destination-side account filters and tightly defined event contracts. For isolated business units, account-specific permissions may provide clearer ownership and a smaller blast radius. Revisit the choice when accounts are reorganized, because the authorization model determines which new accounts can publish without another policy change.
Configuration checklist
- Record both account IDs, bus names, Regions, and the destination bus ARN.
- Confirm the destination Region is supported if the route crosses Regions.
- Attach a destination bus resource policy for the intended sender account or appropriately scoped organization.
- Make the source event pattern as selective as the use case allows.
- Set the destination bus ARN as the source rule target.
- Use an IAM role with
events:PutEventspermission for the destination bus. - Check the role trust policy and resource scope as well as its action permission.
- Add destination-bus rules that match the incoming events and scope
accountto approved sender IDs. - Validate both authorization layers, test the event path, and monitor delivery failures and service metrics.
- Estimate cross-account custom-event charges in the sending account using current AWS pricing.
- Do not plan on relaying received cross-account events onward through a third account using another bus rule.
- Document every source-to-destination relationship so future account or Region changes do not leave stale permissions.
Frequently Asked Questions
Can I send events to a different AWS account without changing the source event bus?
Yes. Keep the source bus, add a rule whose event pattern selects the events, and set the destination account’s bus ARN as the target. The destination bus still needs a resource-based policy, and the target needs an IAM role with events:PutEvents permission.
Is an IAM role required for a cross-account event bus target?
A new cross-account event bus target created after March 2, 2023 must have an IAM role attached. AWS recommends using IAM roles for event bus targets generally, including older configurations.
Should the destination rule include the sender account?
Yes. Include the approved sender account ID in the destination rule’s account pattern. This is especially important when the destination bus accepts events from multiple accounts or an organization.
Who pays for cross-account EventBridge events?
The sending account is charged for cross-account deliveries as custom events. AWS states that the receiving account is not charged for those transferred events; check current pricing for the applicable Region and rate.
Can the receiving account forward the event to another account?
Not by taking the received cross-account event and forwarding it through another event bus rule to a third account. Route directly from the original sender or use another supported fan-out design.
Can the buses be in different Regions as well as different accounts?
Yes, when the destination Region is supported for EventBridge cross-Region delivery. Verify the current supported Region pair before configuring the target.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What should I check when events arrive but downstream processing does not start?
Inspect the destination rule separately from the source rule. Confirm its event pattern, the account condition, and any other detail conditions. A successful transfer to the bus does not guarantee a destination-rule match.
Can I authorize an entire AWS Organization?
A destination bus policy can authorize an appropriately scoped AWS Organization. This can simplify centrally managed environments, but it broadens the trust boundary, so use selective source patterns and explicit account filters on receiving rules.
The Bottom Line
Cross-account EventBridge routing requires both authorization layers: a resource-based policy on the destination bus and an IAM role on the source rule that can call events:PutEvents. Filter at the source, filter again by sender account at the destination, verify Region support, and budget the custom-event charge to the sending account. For multiple consumers, route directly from the original source rather than relying on a cross-account relay chain.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
