Document History for User Guide
The following table describes important changes in each release of the AWS Elemental MediaPackage User Guide after May 2018. For notification about updates to this documentation, you can subscribe to an RSS feed.
-
API version: 1.0
-
Latest documentation update: February 6, 2019
| Change | Description | Date |
|---|---|---|
|
Added DASH Manifest Options topic to discuss the ways that you can modify output DASH manifests. |
February 6, 2019 |
|
|
Added Logging AWS Elemental MediaPackage API Calls with AWS CloudTrail topic to discuss using CloudTrail to log actions in the AWS Elemental MediaPackage API. |
December 21, 2018 |
|
|
Added a Compacted DASH Manifests topic to discuss how compacting DASH output manifests works in AWS Elemental MediaPackage. |
December 18, 2018 |
|
|
Added information about DASH manifest SegmentTemplate format options. |
Added the DASH Manifest Segment Template Format topic to discuss how to change variables in the media URL in the SegmentTemplate element of the DASH manifest. |
December 18, 2018 |
|
AWS Elemental MediaPackage now retains content for 336 hours (14 days). |
November 13, 2018 |
|
|
Added the option to encrypt content keys. Prior to this, AWS Elemental MediaPackage supported clear key delivery only. To use content key encryption, your DRM key provider must support encrypted content keys. If you enable this feature for a key provider that doesn't handle content key encryption, the operation fails. |
November 8, 2018 |
|
|
Added How Input Redundancy Works topic to discuss how AWS Elemental MediaPackage can receive two identical streams for back-up purposes. . |
August 28, 2018 |
|
|
Added sections about working with distributions in CloudFront, including how to create a distribution from the AWS Elemental MediaPackage console. |
August 3, 2018 |
|
|
Added Multi-period DASH in AWS Elemental MediaPackage topic to discuss the purpose and functionality of multiple periods in DASH manifests. |
July 18, 2018 |
|
|
Added Working with CDNs topic to discuss how AWS Elemental MediaPackage works with CDNs such as Amazon CloudFront. |
May 31, 2018 |
|
|
Added Creating Event Notifications topic to discuss using Amazon CloudWatch Events and Amazon Simple Notification Service to notify you of new events. |
January 22, 2018 |
Earlier Updates
The following table describes important changes in each release of the AWS Elemental MediaPackage User Guide before May 2018.
| Change | Description | Date |
|---|---|---|
| Initial document creation. | New document. | November 27, 2017 |
| Corrected links and added whitelisting. | Corrected links to the AWS Elemental MediaPackage console and AWS Elemental MediaPackage
API Reference.
In Working with Endpoints, added reference to access control fields. |
December 1, 2017 |
| Added IAM policy information specific to AWS Elemental MediaPackage. | In Setting Up AWS Elemental MediaPackage, added instructions for creating non-admin roles with limited permissions. | December 13, 2017 |
| Added hard limit information. | In Limits in AWS Elemental MediaPackage, added information about limits that can't be changed (hard limits). | December 20, 2017 |
| Updated IAM policy information. | In Setting Up AWS Elemental MediaPackage, added information about policies specific to AWS Elemental MediaPackage. | January 5, 2018 |
| Added Amazon CloudWatch Events information. | Added Monitoring AWS Elemental MediaPackage with Amazon CloudWatch Events section about the CloudWatch Events that AWS Elemental MediaPackage supports. | February 14, 2018 |
| Added CMAF endpoint information. | Added Creating a Common Media Application Format (CMAF) Endpoint section for new output type. | April 6, 2018 |
| Updated feature functionality. | In Features of AWS Elemental MediaPackage, added feature support for HDR-10. | April 30, 2018 |
| Added content delivery network (CDN) information. | Added topic Working with Content Delivery Networks (CDNs) to discuss how AWS Elemental MediaPackage works with CDNs such as Amazon CloudFront. | May 31, 2018 |
Note
-
The AWS Media Services are not designed or intended for use with applications or in situations requiring fail‐safe performance, such as life safety operations, navigation or communication systems, air traffic control, or life support machines in which the unavailability, interruption or failure of the services could lead to death, personal injury, property damage or environmental damage.
