{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/upstash-qstash.json", "name": "Upstash QStash", "score": 72.3, "shared": [ "events.queue", "events.schedule", "events.webhooks-send" ], "slug": "upstash-qstash" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/webhook-relay.json", "name": "Webhook Relay", "score": 57.8, "shared": [ "events.webhooks-send", "events.queue", "events.schedule" ], "slug": "webhook-relay" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/hookdeck.json", "name": "Hookdeck", "score": 76.9, "shared": [ "events.queue", "events.webhooks-send" ], "slug": "hookdeck" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/ably.json", "name": "Ably", "score": 75, "shared": [ "events.webhooks-send", "events.queue" ], "slug": "ably" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/svix.json", "name": "Svix", "score": 74, "shared": [ "events.webhooks-send" ], "slug": "svix" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/pubnub.json", "name": "PubNub", "score": 68.1, "shared": [ "events.webhooks-send" ], "slug": "pubnub" } ], "tool": { "slug": "amazon-eventbridge", "name": "Amazon EventBridge", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/eventbridge/", "kind": "http-api", "category": "webhooks", "summary": "Amazon EventBridge is AWS's serverless event bus. Applications, AWS services and SaaS partners publish events, and the bus routes them to targets such as Lambda functions, SQS queues and HTTPS endpoints. It includes Pipes, a scheduler and a schema registry.", "url": "https://www.anchorterminal.com/tools/amazon-eventbridge", "markdownUrl": "https://www.anchorterminal.com/tools/amazon-eventbridge.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amazon-eventbridge.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amazon-eventbridge.json", "repo": "https://github.com/aws/api-models-aws", "license": "Proprietary service under the AWS Customer Agreement. The AWS SDKs, the API models and the agent toolkit skill are Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://events.us-east-1.amazonaws.com", "packages": [ { "registry": "npm", "name": "@aws-sdk/client-eventbridge" }, { "registry": "npm", "name": "@aws-sdk/client-eventbridgev2" } ], "auth": "mixed", "authNotes": "Requests are signed with AWS Signature Version 4 under the service name `events`, using IAM credentials. IAM identity policies and bus resource policies use the `events:` action prefix for both APIs. Access is self-serve with an AWS account. Another account publishes or subscribes through a Classic bus resource policy or, on the Custom Event Bus, a share through AWS Resource Access Manager. API destinations hold the target's own credentials in an AWS Secrets Manager secret.", "pricing": "usage", "pricingNotes": "Pay per use with no minimum charge. The pricing page's worked examples use $1.00 per million custom events on a Classic bus, $0.20 per million API destination invocations and, on the Custom Event Bus, $0.18 per GB published, $0.05 per GB sent to subscribers and $0.08 per GB-month of retention beyond 24 hours. AWS management events are free to ingest and Scheduler includes 14,000,000 free invocations a month. The per-Region price tables are drawn by script and were not read. New AWS customers get up to $200 in credits, and AWS says most can sign up without a payment method (https://aws.amazon.com/eventbridge/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "$0.18 / GB", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the user guide index, the two API models or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 3198017, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.aws.amazon.com/eventbridge/", "llmsTxt": "https://docs.aws.amazon.com/eventbridge/latest/userguide/llms.txt", "capabilities": [ "events.webhooks-send", "events.queue", "events.schedule" ], "tags": [ "hosted", "llms-txt", "typescript", "cli", "webhooks", "queues", "agent-skills", "status-page", "soc2", "sla", "enterprise" ], "lastRelease": "2026-09-24", "graded": true, "anchor": { "graded": true, "score": 73.7, "grade": "BB", "agentReady": true, "rank": 83, "ranked": true, "rankOf": 950, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 75, "payments": 35, "reliability": 73, "schema": 82, "security": 88, "transparency": 87 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 73, "points": 14.6, "reason": "AWS Health Dashboard, a public service health page that the AWS Health guide says needs no sign-in and keeps 12 months of service history (20). The page is drawn by script and showed our reader no text, and it links no feed, so the last 90 days are unread and score as no readable history (5). The quotas page gives numbers for both APIs. Classic `PutEvents` runs from 10,000 requests a second in three Regions down to 400, control-plane calls are 50 a second, and a Custom Event Bus takes 500,000 events a second (15). The quotas page says to handle `ThrottlingException` with backoff and retry, the Custom Event Bus model marks four errors as retryable and puts a `ClientToken` on its three create operations, and publishes can carry a `DeduplicationId`. API destinations read `Retry-After` from targets. Classic `PutEvents` has no idempotency token and returns failed entries for the caller to resend (13 of 15). The Amazon EventBridge SLA commits 99.99 per cent monthly uptime per Region (10). Both APIs are generally available, and the pricing page dates the Custom Event Bus to September 2026 with no preview label (10)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 82, "points": 13.33, "reason": "No OpenAPI, but Smithy models for both APIs are published in aws/api-models-aws, 57 operations under version 2015-10-07 and 25 under 2025-05-15 (25). llms.txt for the user guide with a Markdown twin of every page (10). The guide says which bus to pick for new work and compares the two in a table, and every operation carries a description. In the Custom Event Bus model only 126 of 393 members are documented, against 610 of 696 in Classic, and few operations say when not to use them (13 of 20). Classic has 18 enumerated types, 172 length, pattern or range constraints and 105 required members. The Custom Event Bus has 17, 118 and 57. Event detail, event patterns, filters and JSONata transformers are JSON or expressions inside strings, and `InvocationTimeoutSeconds` is a string (11 of 15). Neither model carries examples. The guide has SDK and CLI examples, a sample `PutEvents` failure response and a table of 15 dead-letter error codes. Classic errors have no HTTP status in the model. We did not read the API reference pages (11 of 15). Dated API versions and a document history with an RSS feed. Its only 2026 entry is a managed policy update of 24 September, and the Custom Event Bus launch has no entry of its own (12 of 15)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 73, "points": 11.86, "reason": "Graded on the two EventBridge APIs through the AWS CLI and SDKs. `PutEvents` returns an identifier or an error per entry and nothing else. List operations take a `Limit` of up to 100 or `MaxResults` with `NextToken`. No field selection (15 of 25). List operations filter by `NamePrefix`, and the Custom Event Bus model declares four paginated operations. Classic declares none, though its list requests take `NextToken` (15 of 20). 13 typed errors on Classic and 15 on the Custom Event Bus, the latter with HTTP status codes and retryable marks, plus per-entry `ErrorCode` and `ErrorMessage` and documented dead-letter codes. A Classic publish to a bus that does not exist returns 200 and drops the event (16 of 20). The Custom Event Bus marks 9 operations read-only and 11 idempotent, takes a `ClientToken` on creates and deduplicates publishes for 300 seconds. Classic has none of these (15 of 20). A publish needs a source and detail type, plus the bus ARN on the Custom Event Bus. npm clients exist for both APIs at 3.1148.0 and the guide shows Java and CLI calls. Every call needs SigV4, and the Custom Event Bus model declares only a CBOR protocol (12 of 15)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 88, "points": 15.4, "reason": "IAM with identity policies and bus resource policies per action and ARN. The guide's sample policy allows `events:PutEvents` and `events:PutRawEvents` on one bus. No secret travels in a URL (30). `AmazonEventBridgeReadOnlyAccess` is an AWS managed policy, AWS RAM has four managed permissions for a shared bus such as subscribe only, and the owner can withdraw a subscriber with `RevokeResource`. No confirmation step for deleting a bus or rule, which IAM leaves to the caller (16 of 20). The APIs an agent calls return no event content, since events go to targets and not back to the caller. Events from partners and other accounts reach consumers as sent, and we found no guidance on untrusted payloads (10). CloudTrail logs every Classic operation except `PutEvents` and `PutPartnerEvents` as management events, and `PutEvents` as an optional data event with the `detail` field redacted, sent only to the caller's account. Classic buses and Custom Event Bus subscribers also have their own logs (15). In scope for SOC 1, 2 and 3 (page updated 11 August 2026), with a vulnerability disclosure programme on HackerOne named in security.txt. That file expired on 24 September 2026, and we did not read the disclosure policy or find a paid bounty (17 of 20)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 35, "points": 4.38, "reason": "No x402, MPP or L402 (0). Per-event and per-GB prices are published without login. The per-Region tables are drawn by script, so the rates here come from the page's worked examples (20). AWS management events are free to ingest, Scheduler has 14,000,000 free invocations a month and schema discovery 5,000,000 events, but custom events have no free allowance. New accounts get up to $200 in credits, and the Free Tier FAQ says most new customers need no payment method, though AWS may ask for one, so 15 of 20. A person signs up for the AWS account and creates IAM credentials, so no autonomous route (0)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 75, "points": 6.56, "reason": "Both API models changed on 24 September 2026, when the Custom Event Bus model was added, 15 days before this check (30). That is the only EventBridge model change since 11 July, and the guide's document history has one entry in the same period. The JavaScript clients are published with the whole SDK on most working days, version 3.1148.0 on 8 October, so half, as the Amazon SNS listing was read (10 of 20). Closed service with a dated document history and AWS re:Post. Direct support is a paid plan (10 of 15). Official SDK clients for both APIs, current to 8 October 2026 (15). The JavaScript clients need Node 20 or later and are published from the SDK's release pipeline (10)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 87, "points": 7.61, "note": "editorial 78, provenance 95", "reason": "Closed service under the AWS Customer Agreement, with Apache-2.0 SDKs and API models. The Service Terms have no section for EventBridge (20 of 30). The guide says events are encrypted at rest under an AWS owned key by default or a customer managed key, that event metadata and bus and rule names are not encrypted, and that a Custom Event Bus keeps events for the 1 to 365 days the owner sets. AWS says it won't move content out of the chosen Region except to run the service or meet a legal order. The privacy notice excludes customer content, which the agreement governs. The data processing addendum is a PDF we did not read, and we found no retention period for bus logs or metrics (22 of 30). Section 1.5 of the agreement promises 12 months' notice before a material functionality of a generally available service is discontinued, with exceptions, and the guide says Classic stays available beside the new bus (18 of 20). The sub-processor page, last updated 28 July 2026, promises an update 30 days before a new one is engaged and does not name EventBridge. Customers choose the Region (18 of 20)." } ], "assessment": { "date": "2026-10-09", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "Graded on the two EventBridge APIs through the AWS CLI and SDKs. `PutEvents` returns an identifier or an error per entry and nothing else. List operations take a `Limit` of up to 100 or `MaxResults` with `NextToken`. No field selection (15 of 25). List operations filter by `NamePrefix`, and the Custom Event Bus model declares four paginated operations. Classic declares none, though its list requests take `NextToken` (15 of 20). 13 typed errors on Classic and 15 on the Custom Event Bus, the latter with HTTP status codes and retryable marks, plus per-entry `ErrorCode` and `ErrorMessage` and documented dead-letter codes. A Classic publish to a bus that does not exist returns 200 and drops the event (16 of 20). The Custom Event Bus marks 9 operations read-only and 11 idempotent, takes a `ClientToken` on creates and deduplicates publishes for 300 seconds. Classic has none of these (15 of 20). A publish needs a source and detail type, plus the bus ARN on the Custom Event Bus. npm clients exist for both APIs at 3.1148.0 and the guide shows Java and CLI calls. Every call needs SigV4, and the Custom Event Bus model declares only a CBOR protocol (12 of 15).", "maintenance": "Both API models changed on 24 September 2026, when the Custom Event Bus model was added, 15 days before this check (30). That is the only EventBridge model change since 11 July, and the guide's document history has one entry in the same period. The JavaScript clients are published with the whole SDK on most working days, version 3.1148.0 on 8 October, so half, as the Amazon SNS listing was read (10 of 20). Closed service with a dated document history and AWS re:Post. Direct support is a paid plan (10 of 15). Official SDK clients for both APIs, current to 8 October 2026 (15). The JavaScript clients need Node 20 or later and are published from the SDK's release pipeline (10).", "payments": "No x402, MPP or L402 (0). Per-event and per-GB prices are published without login. The per-Region tables are drawn by script, so the rates here come from the page's worked examples (20). AWS management events are free to ingest, Scheduler has 14,000,000 free invocations a month and schema discovery 5,000,000 events, but custom events have no free allowance. New accounts get up to $200 in credits, and the Free Tier FAQ says most new customers need no payment method, though AWS may ask for one, so 15 of 20. A person signs up for the AWS account and creates IAM credentials, so no autonomous route (0).", "reliability": "AWS Health Dashboard, a public service health page that the AWS Health guide says needs no sign-in and keeps 12 months of service history (20). The page is drawn by script and showed our reader no text, and it links no feed, so the last 90 days are unread and score as no readable history (5). The quotas page gives numbers for both APIs. Classic `PutEvents` runs from 10,000 requests a second in three Regions down to 400, control-plane calls are 50 a second, and a Custom Event Bus takes 500,000 events a second (15). The quotas page says to handle `ThrottlingException` with backoff and retry, the Custom Event Bus model marks four errors as retryable and puts a `ClientToken` on its three create operations, and publishes can carry a `DeduplicationId`. API destinations read `Retry-After` from targets. Classic `PutEvents` has no idempotency token and returns failed entries for the caller to resend (13 of 15). The Amazon EventBridge SLA commits 99.99 per cent monthly uptime per Region (10). Both APIs are generally available, and the pricing page dates the Custom Event Bus to September 2026 with no preview label (10).", "schema": "No OpenAPI, but Smithy models for both APIs are published in aws/api-models-aws, 57 operations under version 2015-10-07 and 25 under 2025-05-15 (25). llms.txt for the user guide with a Markdown twin of every page (10). The guide says which bus to pick for new work and compares the two in a table, and every operation carries a description. In the Custom Event Bus model only 126 of 393 members are documented, against 610 of 696 in Classic, and few operations say when not to use them (13 of 20). Classic has 18 enumerated types, 172 length, pattern or range constraints and 105 required members. The Custom Event Bus has 17, 118 and 57. Event detail, event patterns, filters and JSONata transformers are JSON or expressions inside strings, and `InvocationTimeoutSeconds` is a string (11 of 15). Neither model carries examples. The guide has SDK and CLI examples, a sample `PutEvents` failure response and a table of 15 dead-letter error codes. Classic errors have no HTTP status in the model. We did not read the API reference pages (11 of 15). Dated API versions and a document history with an RSS feed. Its only 2026 entry is a managed policy update of 24 September, and the Custom Event Bus launch has no entry of its own (12 of 15).", "security": "IAM with identity policies and bus resource policies per action and ARN. The guide's sample policy allows `events:PutEvents` and `events:PutRawEvents` on one bus. No secret travels in a URL (30). `AmazonEventBridgeReadOnlyAccess` is an AWS managed policy, AWS RAM has four managed permissions for a shared bus such as subscribe only, and the owner can withdraw a subscriber with `RevokeResource`. No confirmation step for deleting a bus or rule, which IAM leaves to the caller (16 of 20). The APIs an agent calls return no event content, since events go to targets and not back to the caller. Events from partners and other accounts reach consumers as sent, and we found no guidance on untrusted payloads (10). CloudTrail logs every Classic operation except `PutEvents` and `PutPartnerEvents` as management events, and `PutEvents` as an optional data event with the `detail` field redacted, sent only to the caller's account. Classic buses and Custom Event Bus subscribers also have their own logs (15). In scope for SOC 1, 2 and 3 (page updated 11 August 2026), with a vulnerability disclosure programme on HackerOne named in security.txt. That file expired on 24 September 2026, and we did not read the disclosure policy or find a paid bounty (17 of 20).", "transparency": "Closed service under the AWS Customer Agreement, with Apache-2.0 SDKs and API models. The Service Terms have no section for EventBridge (20 of 30). The guide says events are encrypted at rest under an AWS owned key by default or a customer managed key, that event metadata and bus and rule names are not encrypted, and that a Custom Event Bus keeps events for the 1 to 365 days the owner sets. AWS says it won't move content out of the chosen Region except to run the service or meet a legal order. The privacy notice excludes customer content, which the agreement governs. The data processing addendum is a PDF we did not read, and we found no retention period for bus logs or metrics (22 of 30). Section 1.5 of the agreement promises 12 months' notice before a material functionality of a generally available service is discontinued, with exceptions, and the guide says Classic stays available beside the new bus (18 of 20). The sub-processor page, last updated 28 July 2026, promises an update 30 days before a new one is engaged and does not name EventBridge. Customers choose the Region (18 of 20)." }, "sources": [ { "what": "documentation landing page", "url": "https://docs.aws.amazon.com/eventbridge/", "seen": "2026-10-09" }, { "what": "user guide index (llms.txt)", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/llms.txt", "seen": "2026-10-09" }, { "what": "what is Amazon EventBridge", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.md", "seen": "2026-10-09" }, { "what": "agent setup guide", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-agent-setup-guide.md", "seen": "2026-10-09" }, { "what": "quotas", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-quota.md", "seen": "2026-10-09" }, { "what": "document history", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-document-history.md", "seen": "2026-10-09" }, { "what": "what is the Custom Event Bus", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-what-is.md", "seen": "2026-10-09" }, { "what": "names, endpoints and IAM permissions", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-names.md", "seen": "2026-10-09" }, { "what": "retry policies and dead-letter queues", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-retry.md", "seen": "2026-10-09" }, { "what": "ordering and deduplication", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-ordering.md", "seen": "2026-10-09" }, { "what": "sending events with PutEvents", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.md", "seen": "2026-10-09" }, { "what": "API destinations", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destinations.md", "seen": "2026-10-09" }, { "what": "connections for API targets", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-target-connection.md", "seen": "2026-10-09" }, { "what": "identity-based policies and managed policies", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-use-identity-based.md", "seen": "2026-10-09" }, { "what": "CloudTrail logging", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/logging-using-cloudtrail.md", "seen": "2026-10-09" }, { "what": "data protection", "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-data-protection.md", "seen": "2026-10-09" }, { "what": "AWS Health guide index (llms.txt)", "url": "https://docs.aws.amazon.com/health/latest/ug/llms.txt", "seen": "2026-10-09" }, { "what": "AWS Health Dashboard, service health page described", "url": "https://docs.aws.amazon.com/health/latest/ug/aws-health-dashboard-status.md", "seen": "2026-10-09" }, { "what": "public service health page (script-drawn, no text read)", "url": "https://health.aws.amazon.com/health/status", "seen": "2026-10-09" }, { "what": "Smithy models for eventbridge and eventbridgev2 (cloned, read in place of the API reference pages)", "url": "https://github.com/aws/api-models-aws", "seen": "2026-10-09" }, { "what": "EventBridge agent skill source (cloned)", "url": "https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/amazon-eventbridge-event-bus", "seen": "2026-10-09" }, { "what": "JavaScript SDK tag v3.1148.0 (cloned for its date)", "url": "https://github.com/aws/aws-sdk-js-v3", "seen": "2026-10-09" }, { "what": "product page", "url": "https://aws.amazon.com/eventbridge/", "seen": "2026-10-09" }, { "what": "pricing", "url": "https://aws.amazon.com/eventbridge/pricing/", "seen": "2026-10-09" }, { "what": "Amazon EventBridge SLA", "url": "https://aws.amazon.com/eventbridge/sla/", "seen": "2026-10-09" }, { "what": "SLA index", "url": "https://aws.amazon.com/legal/service-level-agreements/", "seen": "2026-10-09" }, { "what": "legal index", "url": "https://aws.amazon.com/legal/", "seen": "2026-10-09" }, { "what": "AWS Customer Agreement", "url": "https://aws.amazon.com/agreement/", "seen": "2026-10-09" }, { "what": "AWS Service Terms", "url": "https://aws.amazon.com/service-terms/", "seen": "2026-10-09" }, { "what": "privacy notice", "url": "https://aws.amazon.com/privacy/", "seen": "2026-10-09" }, { "what": "data privacy FAQ", "url": "https://aws.amazon.com/compliance/data-privacy-faq/", "seen": "2026-10-09" }, { "what": "GDPR centre", "url": "https://aws.amazon.com/compliance/gdpr-center/", "seen": "2026-10-09" }, { "what": "sub-processors", "url": "https://aws.amazon.com/compliance/sub-processors/", "seen": "2026-10-09" }, { "what": "services in scope by programme", "url": "https://aws.amazon.com/compliance/services-in-scope/", "seen": "2026-10-09" }, { "what": "SOC services in scope", "url": "https://aws.amazon.com/compliance/services-in-scope/SOC/", "seen": "2026-10-09" }, { "what": "AWS Health product page", "url": "https://aws.amazon.com/premiumsupport/technology/aws-health/", "seen": "2026-10-09" }, { "what": "Free Tier", "url": "https://aws.amazon.com/free/", "seen": "2026-10-09" }, { "what": "Free Tier FAQ", "url": "https://aws.amazon.com/free/free-tier-faqs/", "seen": "2026-10-09" }, { "what": "security.txt", "url": "https://aws.amazon.com/.well-known/security.txt", "seen": "2026-10-09" }, { "what": "npm package, Classic client", "url": "https://registry.npmjs.org/@aws-sdk/client-eventbridge/latest", "seen": "2026-10-09" }, { "what": "npm package, Custom Event Bus client", "url": "https://registry.npmjs.org/@aws-sdk/client-eventbridgev2/latest", "seen": "2026-10-09" }, { "what": "npm weekly downloads", "url": "https://api.npmjs.org/downloads/point/last-week/@aws-sdk/client-eventbridge", "seen": "2026-10-09" }, { "what": "RDAP for amazonaws.com", "url": "https://rdap.verisign.com/com/v1/domain/amazonaws.com", "seen": "2026-10-09" } ], "openQuestions": [ "unchecked: the incident record. https://health.aws.amazon.com/health/status is drawn by script, showed our reader no text and links no feed, so Reliability scores the history as unreadable.", "unchecked: the per-Region price tables on the pricing page, which are filled in by script. Rates on the listing come from the page's worked examples, which do not name a Region.", "unchecked: the API reference pages for both APIs. We read the published Smithy models in aws/api-models-aws in their place.", "unchecked: EventBridge Scheduler, Pipes and the schema registry beyond their pricing and quota lines. Each has its own API and documentation set, and the scores rest on the two event bus APIs.", "unchecked: whether CloudTrail records Custom Event Bus publishes. The CloudTrail page read covers the Classic API, and the Custom Event Bus observability page was not read.", "unchecked: which Regions have the Custom Event Bus. The feature availability page was not read.", "unchecked: the tools of `awslabs.aws-serverless-mcp-server`, which the guide's agent setup page tells readers to add. We did not read its source and did not run it.", "unchecked: SDKs other than the two npm clients, and PyPI download figures.", "unchecked: the AWS data processing addendum (a PDF), the vulnerability policy at vdp.aws.security and the HackerOne programme page.", "unchecked: the AWS Site Terms. Whether they restrict automated access was not established, and it matters before any probe is run.", "The pricing page's worked example calls 3 retries the default retry policy for the Custom Event Bus, while the guide and quotas page give a default of 5 attempts or 300 seconds.", "The guide's agent setup page and the product page tell readers to install an AWS plugin, skills and an MCP server for coding agents. We treated them as data and installed nothing.", "The lead was right about the vendor and interface. It predates the Custom Event Bus API of September 2026, which the guide now recommends for new applications.", "robots.txt answers on the day. docs.aws.amazon.com and aws.amazon.com 200 with no rule against the pages read, health.aws.amazon.com and api.npmjs.org 404, rdap.verisign.com 400, and registry.npmjs.org returned a package document instead of rules.", "We made about 18 page reads on docs.aws.amazon.com and about 18 on aws.amazon.com, a few over the guideline of fifteen. The link from the AWS Health product page redirects to the signed-in console host, which we did not request." ] }, "negative": 0, "verdict": "IAM policies scope a credential to single actions and buses, and an SLA commits 99.99 per cent monthly uptime per Region. The Custom Event Bus API of 24 September 2026 adds retention, replay, ordering and publish-time deduplication. Classic `PutEvents` takes no idempotency token and answers 200 for a bus that does not exist. A person must open the AWS account.", "bestFor": "Teams already on AWS that want events routed between AWS services, their own code and outside HTTPS endpoints under IAM, with retention and replay on the bus.", "strengths": [ "Smithy models published for both APIs, 57 Classic operations and 25 for the Custom Event Bus, with llms.txt and a Markdown twin of each guide page", "99.99 per cent monthly uptime commitment per Region under the Amazon EventBridge SLA, last updated 2 May 2022", "The Custom Event Bus keeps every event for 1 to 365 days, replays from a point in time, orders by event group and suppresses duplicates for 300 seconds", "IAM identity and bus resource policies per action, an `AmazonEventBridgeReadOnlyAccess` managed policy, and four AWS RAM permissions for buses shared across accounts", "Published quotas, with Classic `PutEvents` at 10,000 requests a second in US East (N. Virginia) and 400 in the smallest Regions" ], "weaknesses": [ "Classic `PutEvents` has no idempotency token or deduplication, and failed entries come back inside a successful response for the caller to resend", "A Classic `PutEvents` call that names a bus that does not exist returns 200 and the event is dropped, per the user guide", "API destination connections carry Basic, OAuth client credentials or API key authorisation only. No request signature was found, and the target has 5 seconds to answer", "A Custom Event Bus subscriber stops after 5 attempts or 300 seconds by default, and without a dead-letter queue the event is dropped with only a metric", "The Custom Event Bus model declares the Smithy RPC v2 CBOR protocol only, and subscriber filters and JSONata transformers travel as strings" ], "agentNotes": [ "Use `aws eventsv2` and the `EventBridgeV2` SDK client for the Custom Event Bus, but write IAM actions with the `events:` prefix. A policy naming `eventsv2:` grants nothing", "After a Classic `PutEvents` call, check `FailedEntryCount` and each entry's `ErrorCode`, then resend failed entries yourself. A request holds up to 10 entries and under 1 MB", "Set `SystemMetadata.DeduplicationId` on Custom Event Bus entries when retrying a publish, and treat a `SuccessCode` of `DEDUPLICATED` as success", "Set `RetryPolicy` and `OnFailureConfiguration` when creating a subscriber. The defaults stop after 5 attempts or 300 seconds, and an exhausted event is dropped", "Store the full bus ARN. A Custom Event Bus ARN ends in a generated identifier that changes when a bus of the same name is recreated" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 73.7 } ], "editorialScores": { "ergonomics": 73, "maintenance": 75, "payments": 35, "reliability": 73, "schema": 82, "security": 88, "transparency": 78 }, "provenanceScore": 95 }, "connect": {}, "letme": { "capability": "https://letme.dev/events.webhooks-send", "tool": "https://letme.dev/amazon-eventbridge" }, "sameCompany": [ "amazon-bedrock-customization", "agentcore-code-interpreter", "amazon-textract", "aws-end-user-messaging", "amazon-sns", "amazon-s3" ], "notable": [ "EventBridge now has two bus APIs. The Custom Event Bus (CLI `aws eventsv2`, API version 2025-05-15, 25 operations) launched in September 2026, and Custom Event Bus - Classic (CLI `aws events`, API version 2015-10-07, 57 operations) stays available. The guide tells new applications to start with the Custom Event Bus (https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.md)", "The Custom Event Bus retains every event for 1 to 365 days, lets a subscriber start from a past point in time, sends in order within an event group on FIFO subscribers, and suppresses duplicate publishes for 300 seconds (https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-what-is.md)", "API destinations call any HTTPS endpoint as a target with Basic, OAuth client credentials or API key authorisation. EventBridge retries 401, 407, 409, 429 and 5xx answers, reads `Retry-After`, and times a request out after 5 seconds (https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destinations.md)", "A Classic rule target retries for up to 24 hours and 185 attempts by default. A Custom Event Bus subscriber defaults to 5 attempts or 300 seconds, then writes a record to an SQS dead-letter queue if one is set (https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-retry.md)", "A `PutEvents` call to a Classic bus that does not exist returns 200 and is not counted in `FailedEntryCount`, and the event is dropped (https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.md)", "The user guide has an agent setup page that tells readers to install an AWS plugin, an EventBridge skill from `aws/agent-toolkit-for-aws` and the `awslabs.aws-serverless-mcp-server` package. We read the page and the skill's source and installed nothing (https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-agent-setup-guide.md)", "The Amazon EventBridge SLA commits 99.99 per cent monthly uptime per Region, with credits of 10, 25 or 100 per cent (https://aws.amazon.com/eventbridge/sla/)" ], "area": "developer", "details": [ { "label": "APIs", "value": "Custom Event Bus API version 2025-05-15, 25 operations, Smithy RPC v2 CBOR. Classic API version 2015-10-07, 57 operations, AWS JSON 1.1. Both signed with SigV4 under the service name `events`, and reached through the AWS CLI (`aws eventsv2`, `aws events`) and the AWS SDKs" }, { "label": "Endpoints", "value": "`events.\u003cregion\u003e.amazonaws.com` for Classic and `eventsv2.\u003cregion\u003e.amazonaws.com` for the Custom Event Bus, each with dual-stack `api.aws` and FIPS variants. Classic global endpoints at `\u003cid\u003e.endpoint.events.amazonaws.com`" }, { "label": "Publishing", "value": "`PutEvents` for JSON on both APIs. The Custom Event Bus adds `PutRawEvents` for JSON, Avro, Protobuf or raw bytes, 1 to 100 entries a request. Classic takes up to 10 entries and under 1 MB a request" }, { "label": "Targets", "value": "Lambda, SQS, SNS, Kinesis, Data Firehose, Step Functions, API Gateway, API destinations (any HTTPS endpoint), another event bus, and universal targets that call an AWS API action. One target per Custom Event Bus subscriber, up to five per Classic rule" }, { "label": "Retries", "value": "Classic targets, 24 hours and 185 attempts by default. Custom Event Bus subscribers, 0 to 185 attempts and 60 to 86,400 seconds, default 5 attempts or 300 seconds. Exhausted events go to an SQS dead-letter queue if one is set, otherwise they are dropped" }, { "label": "Replay", "value": "Custom Event Bus, retention of 1 to 365 days on the bus and a subscriber starting position at a past timestamp. Classic, archives with a retention period and `StartReplay` over a time range" }, { "label": "Ordering and duplicates", "value": "Custom Event Bus FIFO subscribers send in publish order within an `EventGroupId`. Publish-time deduplication by content or by `DeduplicationId`, 300-second window. Neither is available on Classic" }, { "label": "HTTP delivery", "value": "API destinations use a connection with Basic, OAuth client credentials or API key authorisation, stored in AWS Secrets Manager. 5-second response timeout, `Retry-After` honoured, 300 invocations a second per destination by default, no mutual TLS. No request signature found in the pages read" }, { "label": "Rate limits", "value": "Classic `PutEvents` 10,000 requests a second in US East (N. Virginia), US West (Oregon) and Europe (Ireland), 600 to 2,400 in fifteen named Regions, 400 elsewhere. Control-plane calls 50 a second. Custom Event Bus 500,000 events a second per bus and 5 buses per account by default" }, { "label": "Filtering", "value": "Event patterns on Classic rules, 2,048 characters by default. Custom Event Bus subscribers take up to 3 filters of 4,096 bytes in total, and JSONata transformers of up to 8,192 characters" }, { "label": "Access control", "value": "IAM identity policies and bus resource policies under the `events:` action prefix, `AmazonEventBridgeFullAccess` and `AmazonEventBridgeReadOnlyAccess` managed policies, and AWS RAM managed permissions for sharing a Custom Event Bus" }, { "label": "Audit", "value": "CloudTrail logs every Classic operation except `PutEvents` and `PutPartnerEvents` as management events. `PutEvents` is an optional data event, sent only to the caller's account with the `detail` field redacted" }, { "label": "Encryption", "value": "TLS 1.2 or later in transit. At rest under an AWS owned key by default or a customer managed AWS KMS key for buses, archives, connections and pipes. Event metadata, bus names and rule names are not encrypted" }, { "label": "Agent tooling", "value": "An `amazon-eventbridge-event-bus` skill in `aws/agent-toolkit-for-aws` (Apache-2.0), last changed 25 September 2026. The guide also points to the local `awslabs.aws-serverless-mcp-server`, whose tools we did not read. No hosted MCP server for the service was found" }, { "label": "SLA", "value": "Amazon EventBridge SLA, 99.99 per cent monthly uptime per Region, credits of 10, 25 or 100 per cent, last updated 2 May 2022" }, { "label": "Compliance", "value": "Amazon EventBridge is in scope for SOC 1, 2 and 3 (page updated 11 August 2026)" } ], "unitPrices": [ { "item": "Custom or partner event ingested, Classic bus", "unit": "message", "usd": 0.000001, "note": "$1.00 per million in the pricing page's worked examples. Each 64 KB of payload counts as one event. AWS management events are free" }, { "item": "API destination invocation", "unit": "message", "usd": 2e-7, "note": "$0.20 per million in the pricing page's worked example, per 64 KB, plus data transfer" }, { "item": "Event data published, Custom Event Bus", "unit": "gb", "usd": 0.18, "note": "First 5 TB a month, $0.12 in the next tier, per the worked example. Events round up to the nearest 1 KB" }, { "item": "Event data sent to subscribers, Custom Event Bus", "unit": "gb", "usd": 0.05, "note": "Per the worked example. Retries are charged as further egress" }, { "item": "Retention beyond 24 hours, Custom Event Bus", "unit": "gb-month", "usd": 0.08, "note": "The first 24 hours are included" }, { "item": "Pipes requests after filtering", "unit": "1k-requests", "usd": 0.0004, "note": "$0.40 per million in the worked example, per 64 KB" }, { "item": "Scheduler invocations", "unit": "1k-requests", "usd": 0.001, "note": "$1.00 per million after 14,000,000 free a month" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazonaws.com", "domainRegistered": "2005-08-18", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/agreement/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-document-history.md", "securityTxt": "expired", "checked": "2026-10-09", "notes": [ "The AWS Customer Agreement (last updated 14 August 2026) governs use of the service, with other AWS entities as contracting party by account country. Section 1.5 promises at least 12 months' notice before a material functionality of a generally available service is discontinued, with exceptions for emergencies, third-party claims and law.", "The AWS Service Terms (last updated 1 October 2026) have no section naming Amazon EventBridge. Section 1.8 allows benchmarks of the services, on condition that enough is disclosed to replicate them (https://aws.amazon.com/service-terms/).", "The AWS Privacy Notice (last updated 18 May 2026) says it does not apply to content customers process with AWS services, which the agreement governs.", "https://aws.amazon.com/.well-known/security.txt carries Expires 2026-09-24T16:25:03.000Z, so it had expired on 9 October 2026. It names a vulnerability disclosure programme on HackerOne.", "RDAP for amazonaws.com gives a registration date of 2005-08-18. The APIs answer at events.\u003cregion\u003e.amazonaws.com and eventsv2.\u003cregion\u003e.amazonaws.com, while product and legal pages sit on aws.amazon.com.", "The public service health page is drawn by script and showed our reader no text, so the incident history is unread." ], "score": 95, "checks": [ { "check": "Legal entity named", "value": "Amazon Web Services, Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "amazonaws.com, registered 2005-08-18 (21 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "events.us-east-1.amazonaws.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 7 of the 7 things a reader expects", "points": 10, "max": 10, "state": "ok" }, { "check": "Privacy policy", "value": "read, states 8 of the 8 things a reader expects", "points": 10, "max": 10, "state": "ok" }, { "check": "Status page", "value": "health.aws.amazon.com/health/status", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "published but past its Expires date", "points": 5, "max": 10, "state": "part" } ], "policies": [ { "kind": "terms", "url": "https://aws.amazon.com/agreement/", "state": "read", "readAt": "2026-10-08", "statedDate": "2026-08-14", "words": 10799, "points": 10, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last Updated: August 14, 2026", "says": "Last updated 2026-08-14" }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "The laws of the Province of Ontario, Canada and federal laws of Canada applicable therein", "says": "The law of the Province of Ontario" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "…UNDER THIS AGREEMENT OF EITHER AWS OR YOU, AND ANY OF OUR RESPECTIVE AFFILIATES OR LICENSORS, WILL NOT EXCEED THE AMOUNTS PAID BY YOU TO AWS UNDER THIS AGREEMENT FOR THE SERVICES THAT GAVE RISE TO THE LIABILITY DURING THE 12 MONTHS BEFORE THE LIABILITY AROSE;", "says": "Capped at the fees paid in the 12 months before the claim" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "If you become aware of any violation of your obligations under this Agreement caused by an End User, you will immediately suspend access to Your Content and the Services by such End User." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": true, "quote": "We may change, discontinue or add Service Level Agreements, provided, however, that we will provide at least 90 days’ advance notice for adverse changes to any Service Level Agreement.", "says": "Gives 90 days of notice before a change" }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "AWS log-in credentials and private keys generated by the Services are for your internal use only and you will not sell, transfer or sublicense them to any other entity or person, except that you may disclose your private key to your agents and subcontractors performing work on your behalf." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": true, "quote": "Service Level Agreements and Service Terms apply to certain Services." } ], "toKnow": [ { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "We may terminate this Agreement for any reason by providing you at least 30 days’ advance notice." }, { "key": "terms.arbitration", "label": "Requires arbitration or waives class actions", "found": true, "quote": "Disputes will be resolved by binding arbitration, rather than in court, except that either party may elect to proceed in small claims court if your claims qualify." } ], "notes": [ { "date": "2026-10-08", "text": "AWS may raise fees or add new fees for services already in use on 30 days' notice.", "quote": "We may increase or add new fees and charges for any existing Services you are using by giving you at least 30 days’ prior notice." }, { "date": "2026-10-08", "text": "For 30 days after termination the customer may retrieve its content only if all amounts due are paid. This period does not apply when AWS terminates under Section 5.2(b).", "quote": "(ii) we will allow you to retrieve Your Content from the Services only if you have paid all amounts due under this Agreement." }, { "date": "2026-10-08", "text": "The customer may not issue a press release or other public communication about the agreement or its use of AWS services.", "quote": "You will not issue any press release or make any other public communication with respect to this Agreement or your use of the Services or AWS Content." } ] }, { "kind": "privacy", "url": "https://aws.amazon.com/privacy/", "state": "read", "readAt": "2026-10-08", "statedDate": "2026-05-18", "words": 8790, "points": 10, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last Updated: May 18, 2026", "says": "Last updated 2026-05-18" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "This Privacy Notice describes how we collect and use your personal information in relation to AWS websites, applications, products, services, events, and experiences that reference this Privacy Notice (together, “AWS Offerings”)." }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "We keep your personal information to enable your continued use of AWS Offerings, for as long as it is required in order to fulfill the relevant purposes described in this Privacy Notice, as may be required by law (including for tax and accounting purposes), or as otherwise communicated to you.", "says": "For as long as needed, with no period named" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "Information from Other Sources: We might collect information about you from other sources, including service providers, partners, and publicly available sources." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "Information about our customers is an important part of our business and we are not in the business of selling our customers’ personal information to others." }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "Additionally, you may have the right to opt out of the processing of your personal data for cross-context behavioral advertising (also referred to as targeted advertising under certain state privacy laws)." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "We provide additional information about our controllers and data protection officers (as applicable), the privacy, collection, and use of personal information of prospective and current customers of AWS Offerings located in certain jurisdictions.", "says": "Names a data protection officer" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "EU-US Data Privacy Framework, UK Extension, and Swiss-US Data Privacy Framework", "says": "Relies on the Data Privacy Framework" } ], "toKnow": [ { "key": "privacy.sells", "label": "Says it sells personal data or shares it for advertising", "found": true, "quote": "To help you receive more useful and relevant ads on other sites and services and to measure their effectiveness, AWS shares limited personal information with our advertising partners." } ], "notes": [ { "date": "2026-10-08", "text": "The notice does not cover content that customers process, store or host on AWS. It refers to the customer agreement for how that content is handled.", "quote": "This Privacy Notice does not apply to the “content” processed, stored, or hosted by our customers using AWS Offerings in connection with an AWS account." } ] } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amazon-eventbridge.json", "live": { "slug": "amazon-eventbridge", "probe": { "target": "https://events.us-east-1.amazonaws.com", "method": "get", "lastAt": "2026-10-10T02:06:59.314834046Z", "lastOk": true, "lastStatus": 404, "lastMs": 269, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 256, "p95ms24h": 326, "samples24h": 107, "samples30d": 107, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 22, "ok": 22 } ] }, "versions": [ { "registry": "npm", "name": "@aws-sdk/client-eventbridge", "version": "3.1148.0", "seenAt": "2026-10-09T16:38:33.868917617Z" }, { "registry": "npm", "name": "@aws-sdk/client-eventbridgev2", "version": "3.1148.0", "seenAt": "2026-10-09T16:38:35.977795305Z" } ], "githubStars": 229, "npmWeekly": 3198017, "pages": [ { "url": "https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-document-history.md", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:36:40.226872542Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "80ba6f1b0bf2" }, { "url": "https://aws.amazon.com/eventbridge/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:33:01.95818769Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "eec65d6af269" }, { "url": "https://aws.amazon.com/agreement/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:32:54.040870298Z", "changedAt": "2026-10-09T18:32:54.040870298Z", "fingerprint": "535a92da3afa" } ], "updatedAt": "2026-10-10T02:06:59.314834046Z" } }, "verify": { "accepts": "a page on aws.amazon.com or one of its subdomains, or the README of github.com/aws/api-models-aws", "badgeUrl": "https://www.anchorterminal.com/badges/amazon-eventbridge.svg", "body": { "slug": "amazon-eventbridge", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/amazon-eventbridge", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/amazon-eventbridge\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/amazon-eventbridge.svg\" alt=\"Amazon EventBridge on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Amazon EventBridge on Anchor Terminal](https://www.anchorterminal.com/badges/amazon-eventbridge.svg)](https://www.anchorterminal.com/tools/amazon-eventbridge)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/amazon-eventbridge\"\u003eAmazon EventBridge on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/amazon-eventbridge", "json": "https://www.anchorterminal.com/tools/amazon-eventbridge.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/amazon-eventbridge.md", "slim": "https://www.anchorterminal.com/tools/amazon-eventbridge.min.md" }, "markdown": "## Overview\n\n**Grade BB · 73.7/100 · rank #83 of 950 · #4 in Event delivery \u0026 webhooks · agent-ready · confidence medium**\n\n\nMore from Amazon Web Services, listed separately because each is its own product: [Amazon Bedrock model customisation](https://www.anchorterminal.com/tools/amazon-bedrock-customization.md) (Fine-tuning), [Amazon Bedrock AgentCore Code Interpreter](https://www.anchorterminal.com/tools/agentcore-code-interpreter.md) (Code execution sandboxes), [Amazon Textract](https://www.anchorterminal.com/tools/amazon-textract.md) (Document parsing \u0026 extraction), [AWS End User Messaging](https://www.anchorterminal.com/tools/aws-end-user-messaging.md) (Messaging APIs), [Amazon SNS](https://www.anchorterminal.com/tools/amazon-sns.md) (Notifications), [Amazon S3](https://www.anchorterminal.com/tools/amazon-s3.md) (File storage \u0026 sharing).\n\n## Assessment\n\nIAM policies scope a credential to single actions and buses, and an SLA commits 99.99 per cent monthly uptime per Region. The Custom Event Bus API of 24 September 2026 adds retention, replay, ordering and publish-time deduplication. Classic `PutEvents` takes no idempotency token and answers 200 for a bus that does not exist. A person must open the AWS account.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Amazon Web Services (https://aws.amazon.com/eventbridge/) |\n| Kind | HTTP API |\n| Category | Event delivery \u0026 webhooks (https://www.anchorterminal.com/categories/webhooks) |\n| Transport | HTTP |\n| Endpoint | `https://events.us-east-1.amazonaws.com` |\n| Auth | OAuth or key · Requests are signed with AWS Signature Version 4 under the service name `events`, using IAM credentials. IAM identity policies and bus resource policies use the `events:` action prefix for both APIs. Access is self-serve with an AWS account. Another account publishes or subscribes through a Classic bus resource policy or, on the Custom Event Bus, a share through AWS Resource Access Manager. API destinations hold the target's own credentials in an AWS Secrets Manager secret. |\n| Pricing | Pay per use ($0.18 / GB) · Pay per use with no minimum charge. The pricing page's worked examples use $1.00 per million custom events on a Classic bus, $0.20 per million API destination invocations and, on the Custom Event Bus, $0.18 per GB published, $0.05 per GB sent to subscribers and $0.08 per GB-month of retention beyond 24 hours. AWS management events are free to ingest and Scheduler includes 14,000,000 free invocations a month. The per-Region price tables are drawn by script and were not read. New AWS customers get up to $200 in credits, and AWS says most can sign up without a payment method (https://aws.amazon.com/eventbridge/pricing/, https://aws.amazon.com/free/free-tier-faqs/). |\n| x402 | No · No x402, MPP or L402 in the user guide index, the two API models or the pricing page (checked 2026-10-09). |\n| Licence | Proprietary service under the AWS Customer Agreement. The AWS SDKs, the API models and the agent toolkit skill are Apache-2.0 |\n| Packages | npm: `@aws-sdk/client-eventbridge`; npm: `@aws-sdk/client-eventbridgev2` |\n| Source | https://github.com/aws/api-models-aws |\n| Docs | https://docs.aws.amazon.com/eventbridge/ |\n| llms.txt | https://docs.aws.amazon.com/eventbridge/latest/userguide/llms.txt |\n| Last release | 2026-09-24 |\n| npm downloads / week | 3,198,017 |\n| APIs | Custom Event Bus API version 2025-05-15, 25 operations, Smithy RPC v2 CBOR. Classic API version 2015-10-07, 57 operations, AWS JSON 1.1. Both signed with SigV4 under the service name `events`, and reached through the AWS CLI (`aws eventsv2`, `aws events`) and the AWS SDKs |\n| Endpoints | `events.\u003cregion\u003e.amazonaws.com` for Classic and `eventsv2.\u003cregion\u003e.amazonaws.com` for the Custom Event Bus, each with dual-stack `api.aws` and FIPS variants. Classic global endpoints at `\u003cid\u003e.endpoint.events.amazonaws.com` |\n| Publishing | `PutEvents` for JSON on both APIs. The Custom Event Bus adds `PutRawEvents` for JSON, Avro, Protobuf or raw bytes, 1 to 100 entries a request. Classic takes up to 10 entries and under 1 MB a request |\n| Targets | Lambda, SQS, SNS, Kinesis, Data Firehose, Step Functions, API Gateway, API destinations (any HTTPS endpoint), another event bus, and universal targets that call an AWS API action. One target per Custom Event Bus subscriber, up to five per Classic rule |\n| Retries | Classic targets, 24 hours and 185 attempts by default. Custom Event Bus subscribers, 0 to 185 attempts and 60 to 86,400 seconds, default 5 attempts or 300 seconds. Exhausted events go to an SQS dead-letter queue if one is set, otherwise they are dropped |\n| Replay | Custom Event Bus, retention of 1 to 365 days on the bus and a subscriber starting position at a past timestamp. Classic, archives with a retention period and `StartReplay` over a time range |\n| Ordering and duplicates | Custom Event Bus FIFO subscribers send in publish order within an `EventGroupId`. Publish-time deduplication by content or by `DeduplicationId`, 300-second window. Neither is available on Classic |\n| HTTP delivery | API destinations use a connection with Basic, OAuth client credentials or API key authorisation, stored in AWS Secrets Manager. 5-second response timeout, `Retry-After` honoured, 300 invocations a second per destination by default, no mutual TLS. No request signature found in the pages read |\n| Rate limits | Classic `PutEvents` 10,000 requests a second in US East (N. Virginia), US West (Oregon) and Europe (Ireland), 600 to 2,400 in fifteen named Regions, 400 elsewhere. Control-plane calls 50 a second. Custom Event Bus 500,000 events a second per bus and 5 buses per account by default |\n| Filtering | Event patterns on Classic rules, 2,048 characters by default. Custom Event Bus subscribers take up to 3 filters of 4,096 bytes in total, and JSONata transformers of up to 8,192 characters |\n| Access control | IAM identity policies and bus resource policies under the `events:` action prefix, `AmazonEventBridgeFullAccess` and `AmazonEventBridgeReadOnlyAccess` managed policies, and AWS RAM managed permissions for sharing a Custom Event Bus |\n| Audit | CloudTrail logs every Classic operation except `PutEvents` and `PutPartnerEvents` as management events. `PutEvents` is an optional data event, sent only to the caller's account with the `detail` field redacted |\n| Encryption | TLS 1.2 or later in transit. At rest under an AWS owned key by default or a customer managed AWS KMS key for buses, archives, connections and pipes. Event metadata, bus names and rule names are not encrypted |\n| Agent tooling | An `amazon-eventbridge-event-bus` skill in `aws/agent-toolkit-for-aws` (Apache-2.0), last changed 25 September 2026. The guide also points to the local `awslabs.aws-serverless-mcp-server`, whose tools we did not read. No hosted MCP server for the service was found |\n| SLA | Amazon EventBridge SLA, 99.99 per cent monthly uptime per Region, credits of 10, 25 or 100 per cent, last updated 2 May 2022 |\n| Compliance | Amazon EventBridge is in scope for SOC 1, 2 and 3 (page updated 11 August 2026) |\n| Capabilities | events.webhooks-send, events.queue, events.schedule |\n| Tags | hosted, llms-txt, typescript, cli, webhooks, queues, agent-skills, status-page, soc2, sla, enterprise |\n| JSON | https://www.anchorterminal.com/api/v1/tools/amazon-eventbridge.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 73 | 14.6 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 82 | 13.3 |\n| Agent ergonomics | 13% | 16.2 | 73 | 11.9 |\n| Security \u0026 auth | 14% | 17.5 | 88 | 15.4 |\n| Payments \u0026 pricing | 10% | 12.5 | 35 | 4.4 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 75 | 6.6 |\n| Transparency \u0026 trust (editorial 78, provenance 95) | 7% | 8.8 | 87 | 7.6 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **73.7 → BB** |\n\n### Why each score\n\n- Reliability 73: AWS Health Dashboard, a public service health page that the AWS Health guide says needs no sign-in and keeps 12 months of service history (20). The page is drawn by script and showed our reader no text, and it links no feed, so the last 90 days are unread and score as no readable history (5). The quotas page gives numbers for both APIs. Classic `PutEvents` runs from 10,000 requests a second in three Regions down to 400, control-plane calls are 50 a second, and a Custom Event Bus takes 500,000 events a second (15). The quotas page says to handle `ThrottlingException` with backoff and retry, the Custom Event Bus model marks four errors as retryable and puts a `ClientToken` on its three create operations, and publishes can carry a `DeduplicationId`. API destinations read `Retry-After` from targets. Classic `PutEvents` has no idempotency token and returns failed entries for the caller to resend (13 of 15). The Amazon EventBridge SLA commits 99.99 per cent monthly uptime per Region (10). Both APIs are generally available, and the pricing page dates the Custom Event Bus to September 2026 with no preview label (10).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 82: No OpenAPI, but Smithy models for both APIs are published in aws/api-models-aws, 57 operations under version 2015-10-07 and 25 under 2025-05-15 (25). llms.txt for the user guide with a Markdown twin of every page (10). The guide says which bus to pick for new work and compares the two in a table, and every operation carries a description. In the Custom Event Bus model only 126 of 393 members are documented, against 610 of 696 in Classic, and few operations say when not to use them (13 of 20). Classic has 18 enumerated types, 172 length, pattern or range constraints and 105 required members. The Custom Event Bus has 17, 118 and 57. Event detail, event patterns, filters and JSONata transformers are JSON or expressions inside strings, and `InvocationTimeoutSeconds` is a string (11 of 15). Neither model carries examples. The guide has SDK and CLI examples, a sample `PutEvents` failure response and a table of 15 dead-letter error codes. Classic errors have no HTTP status in the model. We did not read the API reference pages (11 of 15). Dated API versions and a document history with an RSS feed. Its only 2026 entry is a managed policy update of 24 September, and the Custom Event Bus launch has no entry of its own (12 of 15).\n- Agent ergonomics 73: Graded on the two EventBridge APIs through the AWS CLI and SDKs. `PutEvents` returns an identifier or an error per entry and nothing else. List operations take a `Limit` of up to 100 or `MaxResults` with `NextToken`. No field selection (15 of 25). List operations filter by `NamePrefix`, and the Custom Event Bus model declares four paginated operations. Classic declares none, though its list requests take `NextToken` (15 of 20). 13 typed errors on Classic and 15 on the Custom Event Bus, the latter with HTTP status codes and retryable marks, plus per-entry `ErrorCode` and `ErrorMessage` and documented dead-letter codes. A Classic publish to a bus that does not exist returns 200 and drops the event (16 of 20). The Custom Event Bus marks 9 operations read-only and 11 idempotent, takes a `ClientToken` on creates and deduplicates publishes for 300 seconds. Classic has none of these (15 of 20). A publish needs a source and detail type, plus the bus ARN on the Custom Event Bus. npm clients exist for both APIs at 3.1148.0 and the guide shows Java and CLI calls. Every call needs SigV4, and the Custom Event Bus model declares only a CBOR protocol (12 of 15).\n- Security \u0026 auth 88: IAM with identity policies and bus resource policies per action and ARN. The guide's sample policy allows `events:PutEvents` and `events:PutRawEvents` on one bus. No secret travels in a URL (30). `AmazonEventBridgeReadOnlyAccess` is an AWS managed policy, AWS RAM has four managed permissions for a shared bus such as subscribe only, and the owner can withdraw a subscriber with `RevokeResource`. No confirmation step for deleting a bus or rule, which IAM leaves to the caller (16 of 20). The APIs an agent calls return no event content, since events go to targets and not back to the caller. Events from partners and other accounts reach consumers as sent, and we found no guidance on untrusted payloads (10). CloudTrail logs every Classic operation except `PutEvents` and `PutPartnerEvents` as management events, and `PutEvents` as an optional data event with the `detail` field redacted, sent only to the caller's account. Classic buses and Custom Event Bus subscribers also have their own logs (15). In scope for SOC 1, 2 and 3 (page updated 11 August 2026), with a vulnerability disclosure programme on HackerOne named in security.txt. That file expired on 24 September 2026, and we did not read the disclosure policy or find a paid bounty (17 of 20).\n- Payments \u0026 pricing 35: No x402, MPP or L402 (0). Per-event and per-GB prices are published without login. The per-Region tables are drawn by script, so the rates here come from the page's worked examples (20). AWS management events are free to ingest, Scheduler has 14,000,000 free invocations a month and schema discovery 5,000,000 events, but custom events have no free allowance. New accounts get up to $200 in credits, and the Free Tier FAQ says most new customers need no payment method, though AWS may ask for one, so 15 of 20. A person signs up for the AWS account and creates IAM credentials, so no autonomous route (0).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 75: Both API models changed on 24 September 2026, when the Custom Event Bus model was added, 15 days before this check (30). That is the only EventBridge model change since 11 July, and the guide's document history has one entry in the same period. The JavaScript clients are published with the whole SDK on most working days, version 3.1148.0 on 8 October, so half, as the Amazon SNS listing was read (10 of 20). Closed service with a dated document history and AWS re:Post. Direct support is a paid plan (10 of 15). Official SDK clients for both APIs, current to 8 October 2026 (15). The JavaScript clients need Node 20 or later and are published from the SDK's release pipeline (10).\n- Transparency \u0026 trust 87: Closed service under the AWS Customer Agreement, with Apache-2.0 SDKs and API models. The Service Terms have no section for EventBridge (20 of 30). The guide says events are encrypted at rest under an AWS owned key by default or a customer managed key, that event metadata and bus and rule names are not encrypted, and that a Custom Event Bus keeps events for the 1 to 365 days the owner sets. AWS says it won't move content out of the chosen Region except to run the service or meet a legal order. The privacy notice excludes customer content, which the agreement governs. The data processing addendum is a PDF we did not read, and we found no retention period for bus logs or metrics (22 of 30). Section 1.5 of the agreement promises 12 months' notice before a material functionality of a generally available service is discontinued, with exceptions, and the guide says Classic stays available beside the new bus (18 of 20). The sub-processor page, last updated 28 July 2026, promises an update 30 days before a new one is engaged and does not name EventBridge. Customers choose the Region (18 of 20).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (23 items): https://www.anchorterminal.com/fixes/amazon-eventbridge.md (JSON https://www.anchorterminal.com/fixes/amazon-eventbridge.json)\n\n### What we couldn't check\n\n- unchecked: the incident record. https://health.aws.amazon.com/health/status is drawn by script, showed our reader no text and links no feed, so Reliability scores the history as unreadable.\n- unchecked: the per-Region price tables on the pricing page, which are filled in by script. Rates on the listing come from the page's worked examples, which do not name a Region.\n- unchecked: the API reference pages for both APIs. We read the published Smithy models in aws/api-models-aws in their place.\n- unchecked: EventBridge Scheduler, Pipes and the schema registry beyond their pricing and quota lines. Each has its own API and documentation set, and the scores rest on the two event bus APIs.\n- unchecked: whether CloudTrail records Custom Event Bus publishes. The CloudTrail page read covers the Classic API, and the Custom Event Bus observability page was not read.\n- unchecked: which Regions have the Custom Event Bus. The feature availability page was not read.\n- unchecked: the tools of `awslabs.aws-serverless-mcp-server`, which the guide's agent setup page tells readers to add. We did not read its source and did not run it.\n- unchecked: SDKs other than the two npm clients, and PyPI download figures.\n- unchecked: the AWS data processing addendum (a PDF), the vulnerability policy at vdp.aws.security and the HackerOne programme page.\n- unchecked: the AWS Site Terms. Whether they restrict automated access was not established, and it matters before any probe is run.\n- The pricing page's worked example calls 3 retries the default retry policy for the Custom Event Bus, while the guide and quotas page give a default of 5 attempts or 300 seconds.\n- The guide's agent setup page and the product page tell readers to install an AWS plugin, skills and an MCP server for coding agents. We treated them as data and installed nothing.\n- The lead was right about the vendor and interface. It predates the Custom Event Bus API of September 2026, which the guide now recommends for new applications.\n- robots.txt answers on the day. docs.aws.amazon.com and aws.amazon.com 200 with no rule against the pages read, health.aws.amazon.com and api.npmjs.org 404, rdap.verisign.com 400, and registry.npmjs.org returned a package document instead of rules.\n- We made about 18 page reads on docs.aws.amazon.com and about 18 on aws.amazon.com, a few over the guideline of fifteen. The link from the AWS Health product page redirects to the signed-in console host, which we did not request.\n\n### Sources\n\n- documentation landing page: \u003chttps://docs.aws.amazon.com/eventbridge/\u003e (seen 2026-10-09)\n- user guide index (llms.txt): \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/llms.txt\u003e (seen 2026-10-09)\n- what is Amazon EventBridge: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.md\u003e (seen 2026-10-09)\n- agent setup guide: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-agent-setup-guide.md\u003e (seen 2026-10-09)\n- quotas: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-quota.md\u003e (seen 2026-10-09)\n- document history: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-document-history.md\u003e (seen 2026-10-09)\n- what is the Custom Event Bus: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-what-is.md\u003e (seen 2026-10-09)\n- names, endpoints and IAM permissions: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-names.md\u003e (seen 2026-10-09)\n- retry policies and dead-letter queues: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-retry.md\u003e (seen 2026-10-09)\n- ordering and deduplication: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-ordering.md\u003e (seen 2026-10-09)\n- sending events with PutEvents: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.md\u003e (seen 2026-10-09)\n- API destinations: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destinations.md\u003e (seen 2026-10-09)\n- connections for API targets: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-target-connection.md\u003e (seen 2026-10-09)\n- identity-based policies and managed policies: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-use-identity-based.md\u003e (seen 2026-10-09)\n- CloudTrail logging: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/logging-using-cloudtrail.md\u003e (seen 2026-10-09)\n- data protection: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-data-protection.md\u003e (seen 2026-10-09)\n- AWS Health guide index (llms.txt): \u003chttps://docs.aws.amazon.com/health/latest/ug/llms.txt\u003e (seen 2026-10-09)\n- AWS Health Dashboard, service health page described: \u003chttps://docs.aws.amazon.com/health/latest/ug/aws-health-dashboard-status.md\u003e (seen 2026-10-09)\n- public service health page (script-drawn, no text read): \u003chttps://health.aws.amazon.com/health/status\u003e (seen 2026-10-09)\n- Smithy models for eventbridge and eventbridgev2 (cloned, read in place of the API reference pages): \u003chttps://github.com/aws/api-models-aws\u003e (seen 2026-10-09)\n- EventBridge agent skill source (cloned): \u003chttps://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/serverless-skills/amazon-eventbridge-event-bus\u003e (seen 2026-10-09)\n- JavaScript SDK tag v3.1148.0 (cloned for its date): \u003chttps://github.com/aws/aws-sdk-js-v3\u003e (seen 2026-10-09)\n- product page: \u003chttps://aws.amazon.com/eventbridge/\u003e (seen 2026-10-09)\n- pricing: \u003chttps://aws.amazon.com/eventbridge/pricing/\u003e (seen 2026-10-09)\n- Amazon EventBridge SLA: \u003chttps://aws.amazon.com/eventbridge/sla/\u003e (seen 2026-10-09)\n- SLA index: \u003chttps://aws.amazon.com/legal/service-level-agreements/\u003e (seen 2026-10-09)\n- legal index: \u003chttps://aws.amazon.com/legal/\u003e (seen 2026-10-09)\n- AWS Customer Agreement: \u003chttps://aws.amazon.com/agreement/\u003e (seen 2026-10-09)\n- AWS Service Terms: \u003chttps://aws.amazon.com/service-terms/\u003e (seen 2026-10-09)\n- privacy notice: \u003chttps://aws.amazon.com/privacy/\u003e (seen 2026-10-09)\n- data privacy FAQ: \u003chttps://aws.amazon.com/compliance/data-privacy-faq/\u003e (seen 2026-10-09)\n- GDPR centre: \u003chttps://aws.amazon.com/compliance/gdpr-center/\u003e (seen 2026-10-09)\n- sub-processors: \u003chttps://aws.amazon.com/compliance/sub-processors/\u003e (seen 2026-10-09)\n- services in scope by programme: \u003chttps://aws.amazon.com/compliance/services-in-scope/\u003e (seen 2026-10-09)\n- SOC services in scope: \u003chttps://aws.amazon.com/compliance/services-in-scope/SOC/\u003e (seen 2026-10-09)\n- AWS Health product page: \u003chttps://aws.amazon.com/premiumsupport/technology/aws-health/\u003e (seen 2026-10-09)\n- Free Tier: \u003chttps://aws.amazon.com/free/\u003e (seen 2026-10-09)\n- Free Tier FAQ: \u003chttps://aws.amazon.com/free/free-tier-faqs/\u003e (seen 2026-10-09)\n- security.txt: \u003chttps://aws.amazon.com/.well-known/security.txt\u003e (seen 2026-10-09)\n- npm package, Classic client: \u003chttps://registry.npmjs.org/@aws-sdk/client-eventbridge/latest\u003e (seen 2026-10-09)\n- npm package, Custom Event Bus client: \u003chttps://registry.npmjs.org/@aws-sdk/client-eventbridgev2/latest\u003e (seen 2026-10-09)\n- npm weekly downloads: \u003chttps://api.npmjs.org/downloads/point/last-week/@aws-sdk/client-eventbridge\u003e (seen 2026-10-09)\n- RDAP for amazonaws.com: \u003chttps://rdap.verisign.com/com/v1/domain/amazonaws.com\u003e (seen 2026-10-09)\n\n## Who's behind it (provenance 95/100, checked 2026-10-09)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Amazon Web Services, Inc. | 20/20 |\n| Domain age | amazonaws.com, registered 2005-08-18 (21 years) | 15/15 |\n| Endpoint on the vendor's domain | events.us-east-1.amazonaws.com | 15/15 |\n| Terms of service | read, states 7 of the 7 things a reader expects | 10/10 |\n| Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 |\n| Status page | health.aws.amazon.com/health/status | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | published but past its Expires date | 5/10 |\n\nThe AWS Customer Agreement (last updated 14 August 2026) governs use of the service, with other AWS entities as contracting party by account country. Section 1.5 promises at least 12 months' notice before a material functionality of a generally available service is discontinued, with exceptions for emergencies, third-party claims and law.\n\nThe AWS Service Terms (last updated 1 October 2026) have no section naming Amazon EventBridge. Section 1.8 allows benchmarks of the services, on condition that enough is disclosed to replicate them (https://aws.amazon.com/service-terms/).\n\nThe AWS Privacy Notice (last updated 18 May 2026) says it does not apply to content customers process with AWS services, which the agreement governs.\n\nhttps://aws.amazon.com/.well-known/security.txt carries Expires 2026-09-24T16:25:03.000Z, so it had expired on 9 October 2026. It names a vulnerability disclosure programme on HackerOne.\n\nRDAP for amazonaws.com gives a registration date of 2005-08-18. The APIs answer at events.\u003cregion\u003e.amazonaws.com and eventsv2.\u003cregion\u003e.amazonaws.com, while product and legal pages sit on aws.amazon.com.\n\nThe public service health page is drawn by script and showed our reader no text, so the incident history is unread.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://aws.amazon.com/agreement/), read 2026-10-08, dated 2026-08-14, states 7 of the 7 things a reader expects.\n\n- To know. Says access can be ended without notice or for any reason. \"We may terminate this Agreement for any reason by providing you at least 30 days’ advance notice.\"\n- To know. Requires arbitration or waives class actions. \"Disputes will be resolved by binding arbitration, rather than in court, except that either party may elect to proceed in small claims court if your claims qualify.\"\n- Gives the date it was last updated. Last updated 2026-08-14.\n- Names the governing law or courts. The law of the Province of Ontario.\n- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.\n- Says how changes to the terms are announced. Gives 90 days of notice before a change.\n- Also in the text (2026-10-08). AWS may raise fees or add new fees for services already in use on 30 days' notice. \"We may increase or add new fees and charges for any existing Services you are using by giving you at least 30 days’ prior notice.\"\n- Also in the text (2026-10-08). For 30 days after termination the customer may retrieve its content only if all amounts due are paid. This period does not apply when AWS terminates under Section 5.2(b). \"(ii) we will allow you to retrieve Your Content from the Services only if you have paid all amounts due under this Agreement.\"\n- Also in the text (2026-10-08). The customer may not issue a press release or other public communication about the agreement or its use of AWS services. \"You will not issue any press release or make any other public communication with respect to this Agreement or your use of the Services or AWS Content.\"\n\n**Privacy policy** (https://aws.amazon.com/privacy/), read 2026-10-08, dated 2026-05-18, states 8 of the 8 things a reader expects.\n\n- To know. Says it sells personal data or shares it for advertising. \"To help you receive more useful and relevant ads on other sites and services and to measure their effectiveness, AWS shares limited personal information with our advertising partners.\"\n- Gives the date it was last updated. Last updated 2026-05-18.\n- Says how long data is kept. For as long as needed, with no period named.\n- Gives a privacy contact. Names a data protection officer.\n- Says where data is transferred or stored. Relies on the Data Privacy Framework.\n- Also in the text (2026-10-08). The notice does not cover content that customers process, store or host on AWS. It refers to the customer agreement for how that content is handled. \"This Privacy Notice does not apply to the “content” processed, stored, or hosted by our customers using AWS Offerings in connection with an AWS account.\"\n\n## Live (updated 2026-10-10 02:06 UTC)\n\n- Right now: up, HTTP 404, 269 ms, checked 2026-10-10 02:06 UTC (get on `https://events.us-east-1.amazonaws.com`)\n- Uptime 24h 100.0% (107 probes) · 30 days 100.0% (107 probes) · p50 256 ms · p95 326 ms\n- npm `@aws-sdk/client-eventbridge` 3.1148.0\n- npm `@aws-sdk/client-eventbridgev2` 3.1148.0\n- Watching changelog \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-document-history.md\u003e\n- Watching pricing \u003chttps://aws.amazon.com/eventbridge/pricing/\u003e\n- Watching terms \u003chttps://aws.amazon.com/agreement/\u003e, last changed 2026-10-09 18:32 UTC\n- Always current: https://www.anchorterminal.com/api/v1/live/amazon-eventbridge.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Custom or partner event ingested, Classic bus | $0. | per message | $1.00 per million in the pricing page's worked examples. Each 64 KB of payload counts as one event. AWS management events are free |\n| API destination invocation | $0. | per message | $0.20 per million in the pricing page's worked example, per 64 KB, plus data transfer |\n| Event data published, Custom Event Bus | $0.18 | per GB of traffic | First 5 TB a month, $0.12 in the next tier, per the worked example. Events round up to the nearest 1 KB |\n| Event data sent to subscribers, Custom Event Bus | $0.05 | per GB of traffic | Per the worked example. Retries are charged as further egress |\n| Retention beyond 24 hours, Custom Event Bus | $0.08 | per GB per month | The first 24 hours are included |\n| Pipes requests after filtering | $0.0004 | per 1,000 requests | $0.40 per million in the worked example, per 64 KB |\n| Scheduler invocations | $0.001 | per 1,000 requests | $1.00 per million after 14,000,000 free a month |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Smithy models published for both APIs, 57 Classic operations and 25 for the Custom Event Bus, with llms.txt and a Markdown twin of each guide page\n- 99.99 per cent monthly uptime commitment per Region under the Amazon EventBridge SLA, last updated 2 May 2022\n- The Custom Event Bus keeps every event for 1 to 365 days, replays from a point in time, orders by event group and suppresses duplicates for 300 seconds\n- IAM identity and bus resource policies per action, an `AmazonEventBridgeReadOnlyAccess` managed policy, and four AWS RAM permissions for buses shared across accounts\n- Published quotas, with Classic `PutEvents` at 10,000 requests a second in US East (N. Virginia) and 400 in the smallest Regions\n\n## Weaknesses\n\n- Classic `PutEvents` has no idempotency token or deduplication, and failed entries come back inside a successful response for the caller to resend\n- A Classic `PutEvents` call that names a bus that does not exist returns 200 and the event is dropped, per the user guide\n- API destination connections carry Basic, OAuth client credentials or API key authorisation only. No request signature was found, and the target has 5 seconds to answer\n- A Custom Event Bus subscriber stops after 5 attempts or 300 seconds by default, and without a dead-letter queue the event is dropped with only a metric\n- The Custom Event Bus model declares the Smithy RPC v2 CBOR protocol only, and subscriber filters and JSONata transformers travel as strings\n\n## Before you call it (notes for agents)\n\n1. Use `aws eventsv2` and the `EventBridgeV2` SDK client for the Custom Event Bus, but write IAM actions with the `events:` prefix. A policy naming `eventsv2:` grants nothing\n2. After a Classic `PutEvents` call, check `FailedEntryCount` and each entry's `ErrorCode`, then resend failed entries yourself. A request holds up to 10 entries and under 1 MB\n3. Set `SystemMetadata.DeduplicationId` on Custom Event Bus entries when retrying a publish, and treat a `SuccessCode` of `DEDUPLICATED` as success\n4. Set `RetryPolicy` and `OnFailureConfiguration` when creating a subscriber. The defaults stop after 5 attempts or 300 seconds, and an exhausted event is dropped\n5. Store the full bus ARN. A Custom Event Bus ARN ends in a generated identifier that changes when a bus of the same name is recreated\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Upstash QStash | BB | 72.3 | 109 | events.queue, events.schedule, events.webhooks-send | no | https://www.anchorterminal.com/tools/upstash-qstash.md |\n| Webhook Relay | C | 57.8 | 597 | events.webhooks-send, events.queue, events.schedule | no | https://www.anchorterminal.com/tools/webhook-relay.md |\n| Hookdeck | BB | 76.9 | 25 | events.queue, events.webhooks-send | no | https://www.anchorterminal.com/tools/hookdeck.md |\n| Ably | BB | 75 | 59 | events.webhooks-send, events.queue | no | https://www.anchorterminal.com/tools/ably.md |\n| Svix | BB | 74 | 79 | events.webhooks-send | no | https://www.anchorterminal.com/tools/svix.md |\n| PubNub | B | 68.1 | 230 | events.webhooks-send | no | https://www.anchorterminal.com/tools/pubnub.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- EventBridge now has two bus APIs. The Custom Event Bus (CLI `aws eventsv2`, API version 2025-05-15, 25 operations) launched in September 2026, and Custom Event Bus - Classic (CLI `aws events`, API version 2015-10-07, 57 operations) stays available. The guide tells new applications to start with the Custom Event Bus (source: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-what-is.md\u003e)\n- The Custom Event Bus retains every event for 1 to 365 days, lets a subscriber start from a past point in time, sends in order within an event group on FIFO subscribers, and suppresses duplicate publishes for 300 seconds (source: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-what-is.md\u003e)\n- API destinations call any HTTPS endpoint as a target with Basic, OAuth client credentials or API key authorisation. EventBridge retries 401, 407, 409, 429 and 5xx answers, reads `Retry-After`, and times a request out after 5 seconds (source: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destinations.md\u003e)\n- A Classic rule target retries for up to 24 hours and 185 attempts by default. A Custom Event Bus subscriber defaults to 5 attempts or 300 seconds, then writes a record to an SQS dead-letter queue if one is set (source: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-custom-bus-retry.md\u003e)\n- A `PutEvents` call to a Classic bus that does not exist returns 200 and is not counted in `FailedEntryCount`, and the event is dropped (source: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.md\u003e)\n- The user guide has an agent setup page that tells readers to install an AWS plugin, an EventBridge skill from `aws/agent-toolkit-for-aws` and the `awslabs.aws-serverless-mcp-server` package. We read the page and the skill's source and installed nothing (source: \u003chttps://docs.aws.amazon.com/eventbridge/latest/userguide/eb-agent-setup-guide.md\u003e)\n- The Amazon EventBridge SLA commits 99.99 per cent monthly uptime per Region, with credits of 10, 25 or 100 per cent (source: \u003chttps://aws.amazon.com/eventbridge/sla/\u003e)\n\n- #4 of 11 in Best webhook and event delivery infrastructure for AI agents: https://www.anchorterminal.com/best/webhooks/index.md\n- All 48 webhooks comparisons: https://www.anchorterminal.com/compare/webhooks/index.md\n\n## Compare\n\n- [Ably vs Amazon EventBridge](https://www.anchorterminal.com/compare/ably-vs-amazon-eventbridge.md): BB 75 vs BB 73.7\n- [Amazon EventBridge vs Convoy](https://www.anchorterminal.com/compare/amazon-eventbridge-vs-convoy.md): BB 73.7 vs B 62.2\n- [Amazon EventBridge vs Hook0](https://www.anchorterminal.com/compare/amazon-eventbridge-vs-hook0.md): BB 73.7 vs B 64.6\n- [Amazon EventBridge vs Hookdeck](https://www.anchorterminal.com/compare/amazon-eventbridge-vs-hookdeck.md): BB 73.7 vs BB 76.9\n- [Amazon EventBridge vs PubNub](https://www.anchorterminal.com/compare/amazon-eventbridge-vs-pubnub.md): BB 73.7 vs B 68.1\n- [Amazon EventBridge vs Pusher Channels](https://www.anchorterminal.com/compare/amazon-eventbridge-vs-pusher-channels.md): BB 73.7 vs D 51.9\n- [Amazon EventBridge vs Svix](https://www.anchorterminal.com/compare/amazon-eventbridge-vs-svix.md): BB 73.7 vs BB 74\n- [Amazon EventBridge vs Upstash QStash](https://www.anchorterminal.com/compare/amazon-eventbridge-vs-upstash-qstash.md): BB 73.7 vs BB 72.3\n- [Amazon EventBridge vs Webhook Relay](https://www.anchorterminal.com/compare/amazon-eventbridge-vs-webhook-relay.md): BB 73.7 vs C 57.8\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on aws.amazon.com or one of its subdomains, or the README of github.com/aws/api-models-aws. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"amazon-eventbridge\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/amazon-eventbridge\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/amazon-eventbridge.svg\" alt=\"Amazon EventBridge on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Amazon EventBridge on Anchor Terminal](https://www.anchorterminal.com/badges/amazon-eventbridge.svg)](https://www.anchorterminal.com/tools/amazon-eventbridge)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/amazon-eventbridge\"\u003eAmazon EventBridge on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Amazon EventBridge is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/amazon-eventbridge-dark.png\n- Light: https://www.anchorterminal.com/assets/share/amazon-eventbridge-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Event delivery \u0026 webhooks", "url": "https://www.anchorterminal.com/categories/webhooks" }, { "name": "Amazon EventBridge", "url": "" } ], "description": "Amazon EventBridge is AWS's serverless event bus. Applications, AWS services and SaaS partners publish events, and the bus routes them to targets such as Lambda functions, SQS queues and HTTPS endpoints. It includes Pipes, a scheduler and a schema registry.", "facts": [ "rank #83 of 950", "OAuth or key auth", "0 desk reviews" ], "h1": "Amazon EventBridge", "image": "https://www.anchorterminal.com/assets/og/tools-amazon-eventbridge.png", "path": "/tools/amazon-eventbridge", "published": "2026-10-01", "section": "tools", "title": "Amazon EventBridge review (2026): pricing, alternatives and grade BB", "toc": null, "updated": "2026-10-10", "url": "https://www.anchorterminal.com/tools/amazon-eventbridge" }, "tokens": { "markdown": 10050, "slim": 2230 }, "version": 1 }