AWS medialive documentation change
Summary
Added documentation for MediaPackage v2 (CMAF) coordination including setup steps and requirements. Updated MediaPackage v1 instructions and reformatted notes.
Security assessment
Changes focus on feature expansion (adding v2 support) and documentation formatting. No security vulnerabilities, weaknesses, or incidents are addressed. The trusted entity permission note is retained but not modified in security context.
Diff
diff --git a/medialive/latest/ug/origin-server-emp.md b/medialive/latest/ug/origin-server-emp.md index 2880574b8..3e5828ae8 100644 --- a//medialive/latest/ug/origin-server-emp.md +++ b//medialive/latest/ug/origin-server-emp.md @@ -4,0 +5,2 @@ +MediaPackage v1 (HLS) coordinationMediaPackage v2 (CMAF) coordination + @@ -9 +11,3 @@ You and the operator of the AWS Elemental MediaPackage service must agree about -Note that you can send to AWS Elemental MediaPackage by creating a MediaPackage output group, or by creating an HLS output group. See [Choosing between the HLS output group and MediaPackage output group](./hls-choosing-hls-vs-emp.html) for a description of the differences. This section describes the first option. +###### Note + +You can send to AWS Elemental MediaPackage by creating a MediaPackage output group or by creating an HLS output group. See [Choosing between the HLS output group and MediaPackage output group](./hls-choosing-hls-vs-emp.html) for a description of the differences. @@ -11 +15,3 @@ Note that you can send to AWS Elemental MediaPackage by creating a MediaPackage -###### To arrange setup of the destination +## MediaPackage v1 (HLS) coordination + +###### To arrange setup of the MediaPackage v1 destination @@ -15 +21,21 @@ Note that you can send to AWS Elemental MediaPackage by creating a MediaPackage - 2. Obtain the ID of the MediaPackage channel. For example, `curlinglive`. The channel ID is case sensitive. + 2. Obtain the ID of the MediaPackage channel. For example, `curling-live`. The channel ID is case sensitive. + + + + +## MediaPackage v2 (CMAF) coordination + +###### To arrange setup of the MediaPackage v2 destination + + 1. Ask the MediaPackage user to create MediaPackage v2 channels in the required regions. Obtain the following information for each destination: + + * AWS region name (for example, `us-east-1` or `eu-west-1`) + + * MediaPackage channel group name + + * MediaPackage channel name + + * Which ingest endpoint (ENDPOINT_1 or ENDPOINT_2) is the preferred input for the MediaPackage channel + + 2. If you plan to use additional destinations for redundancy or cross-region delivery, coordinate the setup of additional MediaPackage v2 channels as needed. + @@ -18,0 +45 @@ Note that you can send to AWS Elemental MediaPackage by creating a MediaPackage +###### Note @@ -20 +47 @@ Note that you can send to AWS Elemental MediaPackage by creating a MediaPackage -Note that you don't need user credentials to send a MediaPackage output group to MediaPackage. MediaLive has permission to write to MediaPackage via the trusted entity. Someone in your organization should have already set up these permissions. For more information, see [Access requirements for the trusted entity](./trusted-entity-requirements.html). +You don't need user credentials to send a MediaPackage output group to MediaPackage. MediaLive has permission to write to MediaPackage via the trusted entity. Someone in your organization should have already set up these permissions. For more information, see [Access requirements for the trusted entity](./trusted-entity-requirements.html).