From 8025542c8e6ca1c2a482dafa0a07fd7c472ab10b Mon Sep 17 00:00:00 2001 From: Pedro Miola Date: Fri, 24 Jan 2025 17:58:29 -0300 Subject: [PATCH] =?UTF-8?q?AI=20Comment:=20The=20documentation=20was=20upd?= =?UTF-8?q?ated=20to=20include=20guidance=20on=20creating=20DNS=20entries?= =?UTF-8?q?=20(CNAME=20or=20ANAME)=20for=20LLHLS=20configurations,=20instr?= =?UTF-8?q?uctions=20on=20inserting=20the=20correct=20certificate=20for=20?= =?UTF-8?q?secure=20setup,=20and=20steps=20for=20validating=20the=20origin?= =?UTF-8?q?=20configuration=20specific=20to=20HLS=20streaming.=20Placehold?= =?UTF-8?q?ers=20were=20added=20for=20detailed=20instructions=20to=20be=20?= =?UTF-8?q?filled=20by=20a=20human=20technical=20writer.=20Additionally,?= =?UTF-8?q?=20a=20section=20for=20additional=20resources=20was=20added=20t?= =?UTF-8?q?o=20address=20the=20need=20for=20references=20or=20case=20studi?= =?UTF-8?q?es=20for=20using=20LLHLS=20via=20TCP=20with=20Azion.=20C=C3=B3d?= =?UTF-8?q?igo:=2016030?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../live-streaming/live-streaming-delivery-hls.mdx | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/src/content/docs/en/pages/architectures/live-streaming/live-streaming-delivery-hls.mdx b/src/content/docs/en/pages/architectures/live-streaming/live-streaming-delivery-hls.mdx index c1373133f5..ae92281737 100644 --- a/src/content/docs/en/pages/architectures/live-streaming/live-streaming-delivery-hls.mdx +++ b/src/content/docs/en/pages/architectures/live-streaming/live-streaming-delivery-hls.mdx @@ -50,8 +50,11 @@ This solution is ideal for content providers who require high fidelity and low l 1. [Create an edge application](/en/documentation/products/guides/build/build-an-application/). 2. [Create a domain](https://www.azion.com/en/documentation/products/guides/configure-a-domain/#create-a-domain-with-azion) and [associate it with the edge application](/en/documentation/products/guides/configure-a-domain/#link-a-custom-domain-to-your-application). 3. Set up and [enforce cache policies for HLS](/en/documentation/products/guides/enforce-hls-cache/) in the edge application. -4. Configure your source and encoder pointing to Azion Ingest DNS entries. -5. Stream your content via Azion Edge Platform. +4. Configure your source and encoder pointing to Azion Ingest DNS entries. + - **Create DNS Entries**: Ensure proper configuration of DNS entries by creating CNAME or ANAME entries to map your domain to Azion's endpoints for LLHLS configurations. [TECHWRITER TODO: INSERT DETAILED STEPS FOR CNAME/ANAME CONFIGURATION] +5. **Insert Correct Certificate**: Ensure the correct SSL/TLS certificate is installed for secure transmission. [TECHWRITER TODO: INSERT DETAILS ON CERTIFICATE INSTALLATION] +6. **Validate Origin Configuration**: Validate your origin configuration specifically for HLS streaming to ensure seamless data flow. [TECHWRITER TODO: INSERT STEPS FOR VALIDATING ORIGIN CONFIGURATION] +7. Stream your content via Azion Edge Platform. --- @@ -60,3 +63,7 @@ This solution is ideal for content providers who require high fidelity and low l - [Azion Edge Network](https://www.azion.com/en/products/our-network/) - [Cache Settings](/en/documentation/products/build/edge-application/cache-settings/) - [Content delivery architecture](/en/documentation/architectures/edge-application/content-delivery/) + +## Additional Resources + +- [TECHWRITER TODO: INSERT INFORMATION ABOUT REFERENCES OR CASE STUDIES FOR USING LLHLS VIA TCP WITH AZION]