Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To send selected events from an Amazon EventBridge bus in one AWS account to a bus in another, authorize the sender on the receiving bus, then create a rule on the sending bus that matches the events to forward and targets the receiving bus ARN. The sender’s target needs an IAM role that can call events:PutEvents on that destination bus; the destination bus also needs a resource-based policy that authorizes the sender. Create receiver-side rules that explicitly match approved sender account IDs.
This guide explains how to route events between EventBridge buses across AWS accounts, including the two-sided permissions, same-Region and supported cross-Region paths, filtering, cost ownership, and constraints that affect multi-account designs.
How cross-account EventBridge routing works
EventBridge routing across accounts uses two buses and a rule on the sending side. The source bus receives events; a rule evaluates each event against its pattern; and matching events are sent to the destination bus ARN as the rule’s target. The receiving bus can then evaluate its own rules and route matching events to its configured targets.
It is not enough to configure a target ARN alone. Delivery crosses an account boundary, so the sender must have permission to put events on the destination bus, and the destination bus must authorize the sender. In practice, that means an IAM role attached to the sender’s event bus target and a resource-based policy on the receiving bus. AWS recommends using IAM roles for event bus targets, and requires a role for new cross-account event bus targets created after March 2, 2023. See Amazon EventBridge’s cross-account guidance and event bus permissions documentation.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
Think of the configuration as two separate decisions: who is allowed to deliver to the destination bus, and which events the sender’s rule should deliver. Keep both narrow. The destination policy defines the trust boundary; the sender’s event pattern defines the routing scope.
Plan the account, bus, and Region path
Before changing policies or rules, record the source and destination account IDs, bus names, bus ARNs, and Regions. A mismatched ARN, account ID, bus name, or Region can make a correct-looking rule fail to deliver.
- Same Region: Cross-account bus routing can be configured between buses in the same Region.
- Different Regions: Cross-Region delivery is also available, but only for supported destination Regions. Check AWS’s current cross-Region event routing guidance for the Region pair you intend to use; availability can change.
- Account boundary: Decide whether to authorize one sender account or a suitably scoped AWS Organization. An organization-wide grant can reduce policy administration in a multi-account environment, but it expands the set of accounts inside the trust boundary.
- Event selection: Decide which events the receiving workload actually needs. Use a specific source-side rule pattern rather than forwarding everything by default.
For multiple sources or destinations, map each origin to its intended destination before creating rules. This makes it easier to see whether the design needs a rule per sender-and-destination path, organization-level authorization, or a supported cross-Region route. It also clarifies which account owns each bus policy, role, rule, and monitoring responsibility.
Recommended Free Tools
Configure the receiving bus policy
Start on the destination side. Add a resource-based policy to the receiving event bus that permits the intended sender account, or an appropriately scoped AWS Organization, to send events. Event bus policies can constrain access by account, organization, rule, or tags. Use the narrowest principal and applicable conditions that fit the design rather than granting broad access without a specific need.
The default event bus can receive events from AWS services, authorized AWS accounts, and PutEvents calls. Cross-account authorization is added through a resource-based policy. The exact policy design depends on whether the trusted principal is an account, organization, or sender role and on any conditions you choose to enforce; consult AWS’s event bus permissions reference for supported policy options.
Keep the resource policy aligned with the sender’s role. The role on the sending rule must be allowed to call events:PutEvents on the destination bus, and the receiving bus policy must authorize the corresponding sender as required by your policy design. If either side is missing or inconsistent, the target may be configured but delivery will not be authorized.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Create the sender rule, target, and IAM role
In the sending account, create a rule on the source bus. Its event pattern should match only the events the receiving account is meant to process. Then set the target to the destination event bus ARN and attach an IAM role that permits events:PutEvents on that bus.
- Select the source bus. Create the rule on the bus that receives the original events, not on the destination bus.
- Define the event pattern. Match the relevant events so unrelated traffic is not forwarded. The pattern is a routing filter, not an authorization policy: it does not replace the receiving bus policy or the target role.
- Set the target ARN. Use the complete ARN for the receiving event bus, including its account and Region. Check these values against the destination bus details you recorded.
- Attach the delivery role. The role needs permission to call
events:PutEventson the specific destination bus. Confirm the role’s trust and permission policies permit the required EventBridge delivery path. - Save and allow for propagation. A newly created or updated target can take a short time to take effect. Do not treat an immediate test failure as proof that the design is wrong until you have checked the configuration and allowed for the update to propagate.
When creating the rule in the AWS console, the console can create the role automatically. When configuring the target through CLI configuration, create the role yourself and verify its trust and permissions. AWS’s event bus targets documentation covers target behavior and configuration notes.
Create receiver-side rules with account filtering
The destination bus receives the forwarded event, but a matching rule on that bus is what triggers downstream processing. Create receiver-side rules for the events the destination account intends to act on, and include an account field containing the approved sender account ID or IDs in the event pattern.
This account check is particularly important when the bus policy authorizes a broad set of senders, such as an organization or multiple accounts. AWS strongly recommends scoping rules to account IDs when a bus accepts events from all accounts, so a rule does not unintentionally match events from unknown senders. For a receiver-side rule intended to match only events generated in the receiving account itself, specify the receiving account explicitly.
Do not assume that the sender-side filter alone is sufficient. The source rule controls what the sender tries to forward; the receiving rule controls which incoming events trigger the destination’s actions. Applying the expected sender account in the receiving pattern provides a separate check at the destination boundary.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Permission and routing responsibilities at a glance
| Configuration | Where it lives | What it controls |
|---|---|---|
| Resource-based bus policy | Receiving account | Which sender account, organization, or otherwise authorized principal may put events on the destination bus. |
| IAM delivery role | Attached to the sender’s event bus target | Whether EventBridge can call events:PutEvents on the destination bus for the target. |
| Sender rule pattern | Sending account, on the source bus | Which source events are selected for forwarding. |
| Destination rule pattern | Receiving account, on the destination bus | Which incoming events trigger the destination’s configured actions; include approved sender account IDs. |
| Target ARN and Region path | Sending account’s target configuration | Which receiving bus is targeted and whether the account/Region route is supported. |
Choose an account and Region design
In a deployment with several accounts, the main trade-off is administrative simplicity versus a narrow trust boundary. Authorizing individual sender accounts keeps the grant explicit, but each new sender may require a policy update. An organization-level grant can make onboarding easier when all member accounts should be eligible, but it should be paired with careful destination-side account filtering and appropriately restricted rules.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
Routing scope also matters. A rule per sender-and-destination path makes the flow explicit and can keep event patterns tailored to the destination’s needs. Direct routing from each origin avoids relying on an intermediate account to relay events onward. That distinction matters because EventBridge does not allow a receiving account to take an event received from a sender account and forward it to a third account using another bus rule.
For Region placement, same-Region routing avoids a cross-Region path; a cross-Region route can serve a destination in another supported Region. Verify the current support guidance for the destination Region rather than assuming every Region pair is valid. Cross-account and cross-Region delivery can be combined only when the destination Region is supported.
As the number of paths increases, account for the operational footprint: bus policies, target roles, sender rules, destination rules, and monitoring points. Keep ownership clear—especially when separate teams manage the sender and receiver—so policy changes, event-pattern changes, and delivery failures have an accountable operator.
Choose the authorization scope deliberately
Account-level and organization-level authorization solve different administration problems. An account-specific grant is the clearer fit when only named producers should publish to a bus: the receiving team can identify each trusted account and review additions individually. The trade-off is that onboarding another producer may mean updating the destination bus policy as well as configuring that producer’s target role and rule.
An organization-scoped grant can simplify access management when a known set of member accounts should be allowed to send, but it should not be treated as a substitute for event filtering. A broad trust boundary increases the importance of explicit account IDs in receiver-side rules and of source patterns that forward only the intended event types. Policies can also use supported conditions to further limit access, including conditions related to rules or tags; choose those controls to match the organization’s ownership model and consult the permissions reference for their exact behavior.
Think through the boundary from both teams’ perspectives. The sender owns its source rule and delivery role; the receiver owns the bus policy and the rules that activate destination actions. In a multi-account platform, document which team approves a new sender, who updates policy, and who investigates a failed path. That operating agreement is part of the routing design, not just paperwork.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
Cost and delivery constraints
AWS bills cross-account event bus delivery to the sending account as custom events; AWS says the receiving account is not charged for those transferred events. Rates and regional details can change, so use the live Amazon EventBridge pricing page for current pricing rather than relying on a fixed amount. For cost ownership, this means the account that configures the forwarding rule should account for transferred-event charges when estimating the route.
There is an important forwarding limitation: an account cannot receive an event from another account on an event bus and then forward that received event onward to a third account through another bus rule. If three accounts need the same original event, architect delivery directly from the original sender to each intended destination, or use another supported fan-out design. Do not build a chain that depends on the intermediate bus relaying a cross-account-received event.
AWS’s newer Custom Event Bus bus-to-bus documentation describes delivery roles, destination bus resource policies or AWS RAM sharing, and best-effort loop detection. Feature details can depend on bus type and the deployment’s applicable capabilities. Avoid relying on loop detection as a design safeguard or on events passing through the same bus multiple times; confirm the relevant feature set in the Custom Event Bus bus-to-bus documentation.
Validate the route and troubleshoot failures
When a forwarded event does not appear to trigger the expected destination action, check the route as a sequence rather than changing policies at random. Verify that the sender rule matches the event, the target ARN points to the intended bus, the role can make the destination call, the destination bus policy authorizes that sender, and a receiver-side rule matches the incoming event and account.
- No event reaches the destination: Confirm the source rule is on the correct bus and its pattern matches the event. Recheck the full target bus ARN, the role attached to that target, the role’s permission for
events:PutEvents, and the receiving bus resource policy. - The event reaches the bus but no destination action runs: Inspect the receiver-side rule pattern, including its
accountfield. Ensure the approved sender account ID is present and that other pattern fields still match the incoming event. - Same-account events match but forwarded events do not: Check whether the receiver rule was explicitly restricted to the receiver’s own account. A rule intended to process cross-account events must allow the approved sender account ID instead.
- Cross-Region delivery does not work: Verify that the destination Region is supported for the intended route and that the target ARN identifies that Region. Use AWS’s current cross-Region guidance rather than assuming support.
- A recent configuration change appears ineffective: Allow a short period for a new or updated target to take effect, then revalidate the policy, role, ARN, and patterns.
Monitor delivery failures and relevant service metrics in the deployment. Metrics and alerts should follow the ownership boundary: the sender’s team needs visibility into forwarding, while the receiver’s team needs visibility into whether incoming events match its rules and reach its targets. The exact monitoring setup depends on the surrounding workload; do not treat a successful target configuration as proof that downstream processing is healthy.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesDeployment checklist
- Record both account IDs, bus names, full bus ARNs, and Regions.
- Confirm the destination Region supports the chosen path if routing across Regions.
- Grant only the intended sender account or appropriately scoped organization access in the destination bus policy.
- Create a source-bus rule with a pattern limited to the events the destination needs.
- Set the destination bus ARN as the target and attach a role with
events:PutEventspermission for that bus. - Check that the target role and receiving bus policy authorize the same intended delivery path.
- Create destination-bus rules that include the expected sender account ID or IDs.
- Allow for target updates to take effect, then validate delivery and monitor failures.
- For multi-destination designs, route from the original sender or select another supported fan-out approach instead of relying on a receiving bus to forward cross-account events onward.
Frequently Asked Questions
Do both AWS accounts need to configure permissions?
Yes. The sending rule’s target needs an IAM role with events:PutEvents permission for the destination bus, and the receiving bus needs a resource-based policy authorizing the intended sender. A target ARN without matching authorization on both sides is not sufficient.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Is an IAM role required for a cross-account event bus target?
AWS requires an IAM role for new cross-account event bus targets created after March 2, 2023, and recommends roles for event bus targets generally. The console can create a role when you configure the rule; with CLI configuration, create and verify the role yourself.
Should I authorize an AWS account or my whole organization?
Use an account-level grant when only specific producer accounts should publish. An appropriately scoped organization grant can simplify onboarding across member accounts, but broadens the trust boundary. In either case, use receiver-side rules that explicitly match approved sender account IDs.
Can the receiving account forward an event to a third account?
Not through another event bus rule when the event was received from a different account. For multiple destinations, route directly from the original sender to each destination or use another supported fan-out design.
Who pays for cross-account EventBridge bus delivery?
AWS bills the sending account for cross-account event bus deliveries as custom events and says the receiving account is not charged for those transferred events. Check the live EventBridge pricing page for current rates and regional details.
Can I route across accounts and Regions at the same time?
Yes, when the destination Region is supported. Confirm the current AWS cross-Region guidance for the specific Region pair and verify that the target ARN names the intended destination Region.
Why did the event arrive but not trigger anything on the receiving side?
The destination bus needs a matching receiver-side rule. Check that its pattern matches the event and includes the approved sender account ID; a rule explicitly limited to the receiving account’s own events will not match events from another account.
The Bottom Line
To route events between EventBridge buses across AWS accounts, authorize the sender in the destination bus policy, configure a source-bus rule that targets the destination ARN with an IAM delivery role, and filter destination rules by approved sender account IDs. Verify the Region path, allow changes to take effect, and design multi-destination delivery from the original sender rather than relying on an intermediate account to forward cross-account events.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
