AWS mediatailor: Note that client-side beacons require Beaconing configuration for logs
Summary
Adds a note explaining that MediaTailor cannot see client-side tracking beacons and pointing readers to Beaconing configuration for CloudWatch metrics and logs.
Security assessment
The addition concerns ad-tracking telemetry and CloudWatch metrics/logs, not security logging or audit; it is operational guidance with no vulnerability addressed.
Evidence
+Because your player sends the beacons in client-side tracking, MediaTailor doesn't see them and can't report on them on its own. To get CloudWatch metrics and logs for the tracking events that your player reports, see [Beaconing configuration](./beaconing-configuration.html).
Diff
diff --git a/mediatailor/latest/ug/ad-reporting-client-side.md b/mediatailor/latest/ug/ad-reporting-client-side.md index 8491959..6f7e59b 100644 --- a//mediatailor/latest/ug/ad-reporting-client-side.md +++ b//mediatailor/latest/ug/ad-reporting-client-side.md @@ -14,0 +15,2 @@ For information about passing player parameters and session data to the ADS for +Because your player sends the beacons in client-side tracking, MediaTailor doesn't see them and can't report on them on its own. To get CloudWatch metrics and logs for the tracking events that your player reports, see [Beaconing configuration](./beaconing-configuration.html). +