AWS mediatailor: MediaTailor Functions overview mentions HTTP response caching
Summary
Adds a bullet in the Functions usage list describing response caching to reduce calls to customer endpoints, and adds a link to the 'Caching HTTP responses' topic in the getting-started list.
Security assessment
This is a purely informational/conceptual addition about caching function responses to lower endpoint traffic; it introduces no auth, encryption, credential, or vulnerability content, and caching shared across sessions is described as a traffic optimization rather than a security control.
Evidence
+ * **Reduce traffic to your endpoints.** Cache function responses and share them across sessions so that MediaTailor calls your endpoint only when it needs fresh data.
Diff
diff --git a/mediatailor/latest/ug/monetization-functions.md b/mediatailor/latest/ug/monetization-functions.md index 6763f8d..36bde95 100644 --- a//mediatailor/latest/ug/monetization-functions.md +++ b//mediatailor/latest/ug/monetization-functions.md @@ -30,0 +31,2 @@ Use Functions when you need to: + * **Reduce traffic to your endpoints.** Cache function responses and share them across sessions so that MediaTailor calls your endpoint only when it needs fresh data. + @@ -58,0 +61,2 @@ If you are new to Functions, start with the [Quick start guide](./monetization-f + * [Caching HTTP responses](./monetization-functions-caching.html) +