AWS eventbridge: X-Ray note on Custom Event Bus trace header propagation
Summary
Adds a note scoping the page to Custom Event Bus - Classic and describing how a Custom Event Bus subscriber propagates trace headers to Step Functions and SQS targets; also renames a nav entry from 'Third-party integrations' to 'Monitoring'.
Security assessment
Purely informational tracing/observability documentation and a navigation label change; no security control, credential, or vulnerability content.
Evidence
This page applies to Custom Event Bus - Classic. A Custom Event Bus subscriber propagates a trace header to Step Functions targets through `StepFunctionsParameters.TraceHeader` and to Amazon SQS targets through `MessageSystemAttributes`; see [Targets for a Custom Event Bus subscriber](./eb-custom-bus-targets.html).
Diff
diff --git a/eventbridge/latest/userguide/eb-related-service-xray.md b/eventbridge/latest/userguide/eb-related-service-xray.md index 2d4525252..46012205b 100644 --- a//eventbridge/latest/userguide/eb-related-service-xray.md +++ b//eventbridge/latest/userguide/eb-related-service-xray.md @@ -10,0 +11,4 @@ You can use AWS X-Ray to trace [events](./eb-events.html) that pass through Even +###### Note + +This page applies to Custom Event Bus - Classic. A Custom Event Bus subscriber propagates a trace header to Step Functions targets through `StepFunctionsParameters.TraceHeader` and to Amazon SQS targets through `MessageSystemAttributes`; see [Targets for a Custom Event Bus subscriber](./eb-custom-bus-targets.html). + @@ -51 +55 @@ Interface VPC Endpoints -Third-party integrations +Monitoring