AWS b2bi documentation change
Summary
Added S3 location fields for validation reports in event schemas and updated examples.
Security assessment
Documents storage of validation reports in S3, which introduces security considerations for sensitive data storage. However, no explicit security guidance is added about access controls or encryption.
Diff
diff --git a/b2bi/latest/userguide/events-detail-reference.md b/b2bi/latest/userguide/events-detail-reference.md index 02ab3fe92..fde5194ef 100644 --- a//b2bi/latest/userguide/events-detail-reference.md +++ b//b2bi/latest/userguide/events-detail-reference.md @@ -72 +72,4 @@ The `source` and `detail-type` fields are included because they contain specific - "validation-status" : "string" + "validation-status" : "string", + "validation-report-s3-location" : { + "bucket" : "string", + "object-key" : "string" @@ -198 +201,6 @@ The format for the output file, `X12`. Only populated for Outbound EDI transform -Only populated for Outbound EDI Transformation Completed events. Value is one of `SUCCEEDED`, `FAILED`, or `NOT_ATTEMPTED`. +Value is one of `SUCCEEDED`, `FAILED`, or `NOT_ATTEMPTED`. + +`validation-report-s3-location` + + +The location in Amazon S3 where the validation report is stored. @@ -249 +257,5 @@ The `source` and `detail-type` fields are included because they contain specific - "validation-status": "FAILED" + "validation-status": "FAILED", + "validation-report-s3-location": { + "bucket": "amzn-s3-demo-bucket", + "object-key": "tp-abc123def456gh789/VALIDATION_REPORT/456_9876_15txn.x12.2025-08-22T21:30:45.123Z.json.validation-errors.txt" + } @@ -325,0 +338,5 @@ Indicates the validity of the original (pre-split) EDI file. Possible values: +`validation-report-s3-location` + + +The location in Amazon S3 where the validation report is stored. For example: +