AWS media edge adds 14-day time-shifted viewing for live streams

This update reduces the architectural friction between live delivery and catch-up services, a critical edge for broadcasters competing with native VOD platforms. By extending the window to 14 days, AWS allows operators to bypass complex external recording workflows for shorter-tail catch-up rights. For the ecosystem, this moves 'Live-to-VOD' from a separate post-process to a native function of the packaging tier, potentially reducing storage overhead and egress costs. Watch for whether high-concurrency sports streamers adopt this for instant-replay features, testing MediaPackage's throttling limits during peak event spikes.

AWS Elemental MediaPackage's time-shifted viewing capability positions the service as a native catch-up and start-over solution within the AWS media stack, eliminating the need for separate DVR or recording infrastructure for windows up to 14 days. The feature works by defining a startover window on an origin endpoint, after which playback requests with start and end parameters receive manifests for the requested timeframe. AWS documentation specifies that the maximum startover window is 1,209,600 seconds, or 14 days, and that requests outside the configured window return an HTTP 404. This approach contrasts with traditional architectures where operators maintain separate origin servers or object-storage buckets for catch-up content, adding operational complexity and egress costs.

For operators evaluating MediaPackage's time-shifted viewing, AWS recommends using consistent playback windows across player sessions rather than generating unique start or end times per viewer. The company's guidance notes that unique per-viewer parameters degrade CDN caching efficiency and can trigger throttling at the MediaPackage level. This is a practical consideration for high-concurrency live events such as sports, where thousands of viewers may request slightly different start times simultaneously. The trade-off between personalization and cache performance is a key architectural decision for teams adopting this feature at scale.

AWS Elemental MediaPackage also supports harvesting clips from the time-shifted window into standalone VOD assets, a workflow the company documents as "Creating live-to-VOD assets." The Boto3 API reference confirms that the StartoverWindowSeconds parameter on create_origin_endpoint accepts values up to 1,209,600 seconds, giving developers programmatic control over the catch-up window per endpoint. For teams already using AWS Elemental MediaLive for encoding and Amazon CloudFront for delivery, this keeps the entire live-to-catch-up pipeline within a single cloud provider's billing and monitoring surface, reducing integration overhead compared to multi-vendor stacks.