EventBridge Integration

Parent: MongoDB Atlas AWS Networking · Published reference · snapshot 2026-10-15

Depth-first rabbithole dossier for EventBridge Integration; source-anchored research pack.

These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.

How it works

[low] When a partner event source is associated with an event bus, the status of the event source changes from `Pending` to `Active`, and the name of the event bus updates to match the partner event source name. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-saas.html [source]
[low] The `PutEvents` action sends multiple events to EventBridge in a single request, attempting to process all entries in the natural order of the request, and after the call, EventBridge assigns each event a unique ID. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]
[low] When sending custom events to EventBridge using the `PutEvents` action, you can batch up to 10 event entries into one request for efficiency. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]

Measurements and reference values

[low] If the entry size for `PutEvents` is larger than 1 MB (1,048,576 bytes), it is recommended to upload the event to an Amazon S3 bucket and include the `Object URL` in the `PutEvents` entry. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]

Problems, failure modes and limitations

[low] Individual entries for an EventBridge Trigger event must be smaller than 1 MB, and if an entry exceeds this limit, EventBridge throws an error with either status code 400 (total size of the entries in the request is over the limit) or status code 413 (payload too large). Sources: https://www.mongodb.com/docs/atlas/atlas-ui/triggers/aws-eventbridge.md [source]
[low] Only the partner account of the event source associated with a partner event bus is permitted to send events to it, and calling `put-permission` on a partner event bus returns an error. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-saas.html [source]
[low] Including an `AWS::Events::EventBusPolicy` resource for the partner event bus in your template will result in an error. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-saas.html [source]
[low] The size limit for `PutEvents` is imposed on the entry, and even if the entry is less than the size limit, the event in EventBridge is always larger than the entry size due to the necessary characters and keys of the JSON representation of the event. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]
[low] If an error is received from EventBridge, the event processor parses the error as either `DOCUMENT_TOO_LARGE` or `OTHER`. Sources: https://www.mongodb.com/docs/atlas/atlas-ui/triggers/aws-eventbridge.md [source]

Comparisons and alternatives

[low] The total request size for `PutEvents` must be less than 1 MB (1,048,576 bytes), a limit that applies to the request as a whole rather than individual entries, meaning a single event can use up to the full 1 MB if it is the only entry in the request. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]

Facts and statements

[low] To receive events from SaaS partner applications and services, you need a partner event source from the partner, and any events published to a partner event source not associated with an event bus are immediately dropped and not persisted at rest in EventBridge. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-saas.html [source]
[low] The response `Entries` array from `PutEvents` always includes the same number of entries as the request array, with successful entries including an `Id` value and unsuccessful entries including `ErrorCode` and `ErrorMessage` values. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]
[low] By default, if an individual entry within a `PutEvents` request fails, EventBridge continues processing the rest of the entries in the request. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]
[low] In `PutEvents` requests, the `Time` parameter is 14 bytes if specified, while the `Source`, `DetailType`, `Detail`, and each entry of the `Resources` parameters are counted by the number of bytes for their UTF-8 encoded forms if specified. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]
[low] MongoDB Atlas on AWS enables global scaling without limits using elastic clusters, bi-directional auto-scaling, independent operational/analytics/search nodes, and Amazon Bedrock integration. Sources: https://aws.amazon.com/marketplace/pp/prodview-pp445qepfdy34 [source]
[low] If you use `PutEvents` to publish an event to an event bus that does not exist, EventBridge event matching will not find a corresponding rule and will drop the event, sending a `200` response without failing the request or including the event in the `FailedEntryCount` value. Sources: https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-putevents.html [source]

Related concepts

EventBridge — is a part of EventBridge Integration
Integration — is a part of EventBridge Integration

Children

No children recorded.

← the whole tree · 3D view· how to read this page