AWS mediatailor documentation change
Summary
Added troubleshooting section for manifest-related alerts with verification steps for source requirements, manifest logs, error codes, and format checks
Security assessment
The changes provide general troubleshooting guidance for manifest errors but do not address specific security vulnerabilities or introduce security features.
Diff
diff --git a/mediatailor/latest/ug/channel-assembly-alerts.md b/mediatailor/latest/ug/channel-assembly-alerts.md index 3e8819746..a6de75ae1 100644 --- a//mediatailor/latest/ug/channel-assembly-alerts.md +++ b//mediatailor/latest/ug/channel-assembly-alerts.md @@ -5 +5 @@ -Viewing alertsHandling alerts +Troubleshooting manifest-related alertsViewing alertsHandling alerts @@ -7 +7 @@ Viewing alertsHandling alerts -# Receiving AWS Elemental MediaTailor Channel Assembly alerts +# Receiving AWS Elemental MediaTailor channel assembly alerts @@ -40,0 +41,15 @@ Channel | `PROGRAM_ALERT` | The program `programName` contained in this channel +## Troubleshooting manifest-related alerts + +When you encounter manifest-related alerts such as `UNPARSABLE_MANIFEST`, `VARIANT_DURATION_MISMATCH`, or `TARGET_DURATION_MISMATCH`, check the following: + + 1. **Verify source requirements** : Ensure your content meets the requirements outlined in [Integrating a content source for MediaTailor ad insertion](./integrating-origin.html). + + 2. **Check manifest logs** : For detailed manifest error analysis and event types, see [AWS Elemental MediaTailor manifest logs description and event types](./log-types.html). + + 3. **Check error codes** : For detailed error analysis, see [Troubleshooting MediaTailor](./troubleshooting.html). + + 4. **Review manifest format** : Verify that your manifest follows the correct format specifications for your streaming protocol (HLS or DASH). + + + +