The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →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
Amazon EventBridge event bus costs depend on what kind of event you publish, how large it is, where it goes, and which optional features handle it. AWS management events are free to ingest under AWS’s pricing page, but partner and custom events can incur ingestion charges. Delivery, cross-account routing, archives and replay, Schema Discovery, API Destinations, and cross-Region activity can add separate charges. To estimate a bill, count billable payload chunks and trace each event’s route—not just the number of logical events your application produces.
What affects the cost of an EventBridge event bus?
There is no single per-event figure that describes every EventBridge workload. AWS distinguishes event categories and delivery paths, and optional features introduce their own meters. Payload size matters because a large event can count as multiple billable event units. The relevant AWS Region also matters: rates and feature availability should be checked for the Region in which the system runs.
For a useful estimate, separate the bill into the stages and features your design actually uses: event ingestion, delivery to buses or services, cross-account and cross-Region paths, archival and replay, Schema Discovery, and API Destinations. Pipes and Scheduler are separate products with separate pricing models; include them only when they are part of the architecture. AWS’s EventBridge pricing page is the primary place to verify current pricing.
How do event type and destination change the bill?
AWS’s pricing page distinguishes AWS management events, partner events, and custom events. It describes AWS management events as free to ingest, while partner and custom events have ingestion charges. That does not mean all events or all processing are free: an event’s origin and its delivery route can affect the charge.
#1 Best Overall
In particular, AWS’s pricing examples distinguish delivery within an account from delivery across accounts. They illustrate different paths: an AWS management event sent to a service in another account; partner events, some of which cross account boundaries; and custom events published in one account, forwarded to another account’s bus, and then delivered to a service. Model each part of the path rather than applying one assumed charge to every event.
- Ingestion: identify whether events are AWS management, partner, or custom events, then apply the relevant current regional rate or free treatment.
- Delivery: record whether an event goes to a bus or to a service, and whether the destination is in the same account or another account.
- Multiple hops: count every bus and target in the route. Forwarding to another bus and then delivering to a service are distinct routing steps to evaluate against AWS’s pricing rules.
AWS’s examples are illustrations, not a substitute for recalculating your own workload. In particular, do not assume that a free ingestion category makes every subsequent delivery free, or that a partner event has the same price as a custom event on every route. For the precise rules and examples, consult the live AWS pricing page and the EventBridge FAQ.
Why payload size matters: EventBridge uses 64 KB chunks
For event bus pricing, AWS counts each 64 KB payload chunk as one event unit. A 256 KB payload therefore counts as four units, not one. In general, estimate with the event’s size and the applicable 64 KB chunking rule, rather than treating every logical event as a single billable unit.
This difference can materially change a forecast when an application publishes large payloads. For example, a workload producing 100,000 events is not necessarily equivalent to 100,000 billable units: if those events have payloads that count as four chunks apiece, the corresponding bus metering is based on 400,000 units before applying the applicable rates and routing rules. This is a unit-count illustration, not a total-price calculation; AWS’s current regional rates and the event path are still needed to calculate charges.
Use the payload size distribution, not just an average event count. If events differ in size, estimate the quantities in each size band and count the applicable chunks for each band. This makes it easier to see whether a change to event content, such as adding fields or carrying larger data inline, changes the billable volume even when the number of messages stays the same. AWS’s pricing page describes the 64 KB event unit rule: Amazon EventBridge pricing.
Rank #2
What do cross-account delivery, Regions, and replication add?
Cross-account delivery may be charged differently from delivery to a service in the same account. Cross-Region traffic can also incur standard AWS data transfer charges. When an event crosses both kinds of boundary, record both; an account boundary and a Region boundary are separate facts about the route, and one should not be used as a proxy for the other.
AWS’s FAQ separately states a charge of $1 per million events for replication of cross-Region events. Treat that as a distinct replication price rule, not as a general rate for every event sent across Regions. Confirm that your implementation uses the relevant replication feature and check the live FAQ and pricing information before applying it to an estimate. Standard data transfer charges may also apply to inter-Region traffic, so do not assume the replication price replaces all network charges.
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 glitchesA route inventory is the most reliable way to catch these effects. For each event flow, write down its source, each event bus and target, the account for each step, and the Region for each step. Then distinguish the delivery or replication feature used from the data transfer the route generates. AWS’s FAQ and pricing page explain the applicable billing scope: EventBridge FAQs and EventBridge pricing.
How do archive and replay charges work?
An event archive adds more than the cost of initially publishing an event. AWS’s pricing page identifies storage, archive processing, and replayed events as chargeable components. A forecast should therefore account for how much data is retained, for how long, which events qualify for retention, and how much archived data is replayed.
Archives can filter the events they retain and can be configured with a retention period. AWS’s archive documentation says retention can default to indefinite unless a period is configured. An unbounded retention setting can therefore make the volume and duration assumptions in an estimate important: consider the retained data over time, rather than budgeting only for the stream of newly published events.
Rank #3
Replay also has operational details that affect planning. Replayed events return to the source event bus, and AWS does not guarantee that they are replayed in the order they originally arrived. Events may take time to reach an archive; AWS recommends waiting 10 minutes before replaying recently received events to help ensure they have arrived. These details matter when estimating the replay volume and when deciding how a replay fits into the event flow, although the recommendation is not a pricing allowance.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use AWS’s archive and replay documentation for behavior and configuration details, and the pricing page for the current archive, storage, and replay meters. Do not count only the initial event publication when archives are enabled.
Is Schema Registry free, and does Schema Discovery cost extra?
AWS states that use of the Schema Registry is free. Schema Discovery is a separate feature with its own event-based pricing: AWS lists a free tier of 5 million ingested events per month, and its FAQ states that usage beyond that tier costs $0.10 per million ingested events. These figures describe Schema Discovery, not the Schema Registry as a whole; verify the live AWS pricing page and FAQ because pricing terms can change.
Discovery metering uses a different payload chunk size from event bus pricing. AWS counts each 8 KB chunk as one ingested event for Schema Discovery. Thus, the 64 KB event bus unit should not be reused to calculate discovery usage. A large payload may count as multiple discovery events even when you have counted its bus units separately.
For an estimate, determine whether discovery is enabled, how many events it processes in the billing month, and their sizes under the 8 KB rule. Then apply the monthly free tier and the listed overage rate. Keep those discovery calculations separate from the free Registry and from event bus ingestion and delivery. See AWS’s pricing page and FAQ.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC 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 & 11What do API Destinations add to the estimate?
API Destinations have their own invocation metering. AWS counts 64 KB chunks as separate requests for this purpose, so the number of outbound invocations alone may not capture all billable request units for larger payloads.
There may also be connectivity costs beyond invocation metering. AWS warns that traffic to public internet endpoints can incur standard data transfer charges. For private connectivity, PrivateLink or VPC Lattice charges may apply. Include the actual connection path in the estimate—public endpoint versus private connectivity—and account for the associated network service rather than treating the invocation figure as the total cost.
The pricing page provides the applicable API Destination details and should be checked for the selected Region: Amazon EventBridge pricing. The AWS pricing page does not establish a single invocation rate that applies in every Region, so use the live page rather than extrapolating a total from the metering description alone.
Are Pipes and Scheduler part of event bus pricing?
No. EventBridge Pipes and EventBridge Scheduler appear alongside event bus pricing on AWS’s pricing page, but they have separate pricing models. They are relevant to a total architecture estimate only if your design uses them; their charges should not be folded into a universal event bus rate.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Pipes: AWS describes request pricing and payload chunks. Check the current Pipes terms and rates on the AWS pricing page if a Pipe is in the workflow.
- Scheduler: AWS’s pricing page currently displays a free-tier allowance of 14 million invocations per month. This is a Scheduler allowance, not an event bus allowance, and it should be verified on the live page before use in a forecast.
Feature availability varies by Region, so confirm both that a feature is available where you plan to use it and that its price terms match that Region. AWS publishes an EventBridge feature-availability by Region table and current pricing at EventBridge pricing.
Best Value
How to build an EventBridge cost estimate
Start with a billing period and a diagram of the event flow. Gather the inputs below before multiplying anything by a rate; omitting even one boundary or optional feature can make two otherwise similar estimates incomparable.
- Classify the source events. Separate AWS management events, partner events, and custom events. Apply AWS’s current ingestion treatment to each category rather than assuming one category’s rule applies to the others.
- Count events by billing period and route. Record the number published and delivered, then split flows by destination and any intermediate bus. This gives you the volume to which the relevant ingestion and delivery meters apply.
- Group payloads by size. Apply 64 KB chunks for event bus pricing, including the four units AWS assigns to a 256 KB payload. Do not substitute the logical message count for chunked units.
- Mark account boundaries. For each delivery step, note whether it stays in the account or goes to another account, because the pricing examples distinguish those cases.
- Mark Region boundaries and replication. Identify inter-Region data transfer and whether cross-Region replication is used. Evaluate the FAQ’s replication charge separately from possible standard data transfer charges.
- Include archives only where configured. Record archive filters, retained data volume, retention duration, and expected replay volume. Include the AWS-listed storage, processing, and replay components.
- Calculate discovery separately. If Schema Discovery is enabled, count its ingested events using 8 KB chunks, then account for its 5 million monthly free tier and listed overage terms. Do not charge the Registry as though it were Discovery.
- Identify outbound API connectivity. For API Destinations, estimate invocation chunks and note public internet, PrivateLink, or VPC Lattice connectivity so applicable network charges are not missed.
- Add only in-scope adjacent services. Include Pipes or Scheduler if used, applying their distinct pricing models and checking current terms. Do not include them as automatic event bus charges.
- Check the Region and live rates. Verify feature availability and pricing for the actual AWS Region, then recalculate each scenario using the live AWS pricing page and relevant service terms.
For a scenario comparison, keep the inputs above constant except for the architecture choice you are testing—for example, same-account versus cross-account delivery, archive retention, or public versus private API connectivity. That isolates which design choice changes the estimate. The AWS pages cited here do not provide a complete region-by-region rate table, so a defensible total requires the live rates for your Region and the details of your workload.
What should you verify before relying on the number?
AWS pricing pages and free-tier terms can change, and the amount owed depends on the Region and features in use. The listed discovery and Scheduler allowances, discovery overage rate, and replication figure above are AWS service pricing terms, not independent benchmark results or an account-specific quote. Confirm their current wording before budgeting or approving a design.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a final estimate, reconcile the design diagram against the billable inputs: category, count, size, destination, account and Region boundaries, archive lifecycle, replay volume, discovery usage, API connection path, and any separate Pipes or Scheduler usage. If any of these are unknown, treat the estimate as incomplete rather than applying an unsupported flat per-event price.
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.
