Trigger Project Expression before EventBridge entry-size validation
Parent: EventBridge Integration · Published reference · snapshot 2026-11-02
↓ Facts as markdownall context files
Source-anchored research for Trigger Project Expression before EventBridge entry-size validation. Run status: COMPLETED.
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.
Definitions
- MongoDB's EventBridge integration guide tells users to reduce the size of their PutEvents entry and explicitly refers to AWS documentation for calculating Amazon PutEvents event entry size. The published reference names the entry-size section of the AWS PutEvents guide. This establishes MongoDB's documented accounting guidance for the integration; it does not identify the SDK operation, exact outgoing entry mapping or internal validator sequence used by a deployed service. (low confidence) [source 1] [source 2]
How it works
- For Database Triggers sending to EventBridge, Project Expression selects fields from the change event and reduces document size before messages are sent to EventBridge. This documents projection on the outgoing path; it does not specify an internal validator call sequence. (medium confidence) [source 1] [source 2]
- The Database Triggers documentation conflicts about allowed projection forms: the Advanced table describes an exclusive projection, while the optimization section says projection is inclusive only, requires operationType, and allows explicitly excluding only _id. Treat exclusion-only acceptance as unresolved; the documented inclusive example uses _id: 0, operationType: 1 and updateDescription.updatedFields.status: 1. (low confidence) [source]
- The version-pinned Crossplane provider schema exposes ConfigProject as an optional string for DATABASE triggers, with JSON name configProject and Terraform name config_project. Its generated comment defines the value as an aggregation projection document filtering fields in change event objects. This is configuration-schema evidence, not proof of runtime byte-validation order or current-provider behavior. (low confidence) [source]
- The Database Triggers guide's Full Document setting identifies `fullDocument` as the field for the modified document after the change. The MongoDB Partners Vehicle-Digital-Twin-Solution README supplies an EventBridge Trigger Project Expression example that selects a vin field from that object and maps measurements into voltage/current pairs. This is an authored example, not a measured size-reduction result or proof that arbitrary computed projections work in every Trigger version. (low confidence) [source 1] [source 2]
Measurements and reference values
- The AWS PutEvents guide snapshot reviewed here counts UTF-8 bytes of Source and DetailType, optional Detail, and each optional Resources string, plus 14 bytes when Time is specified. It says the sum of all event entries in a request must be less than 1 MB (1,048,576 bytes). This request-wide accounting is distinct from measuring only an original database document or counting JSON characters. (low confidence) [source]
Comparisons and alternatives
- On the documented Atlas EventBridge path, Triggers convert BSON types in event objects to standard JSON types by default. Enabling Extended JSON instead serializes event objects to Extended JSON to preserve BSON type information. AWS counts the UTF-8 encoded Detail representation, so a byte comparison concerns the outgoing serialized representation rather than character count or the original BSON object. (medium confidence) [source 1] [source 2]
Children
- No children recorded.