DUPATANE← Back to hands-on labs

AWS · VIDEO ON DEMAND · EDGE DELIVERY

CinemaPlay Beta: 4K adaptive streaming

A working DUPATANE-branded cloud video player with a custom HTTPS domain, private S3 origin, MediaConvert HLS renditions, CloudFront delivery and manual/automatic quality selection.

S3 + OACMediaConvertCloudFrontACM / TLSGoDaddy DNSHLS.js

System architecture

Source video → Private S3
    ↓
AWS Elemental MediaConvert
    ↓
HLS master + 4 rendition playlists + segments
    ↓
Private S3 origin ← CloudFront OAC
    ↓
CloudFront (HTTPS + ACM certificate)
    ↑
GoDaddy subdomain CNAME
    ↓
DUPATANE CinemaPlay player (HLS.js / native HLS)
The page is served from the same distribution as the HLS files, reducing browser cross-origin complications. The source video and private AWS identifiers are not published.

What works

01

4K ABR streaming

The HLS master exposes 3840×2160, 1920×1080, 960×540 and 640×360 renditions. The player shows Auto and manual quality options.

02

Branded clean URL

GoDaddy DNS points a product beta subdomain to CloudFront. An ACM-issued certificate enables HTTPS, and the default root object serves watch.html at /.

03

Private origin, controlled updates

CloudFront OAC protects the S3 origin; scoped IAM controls HTML uploads and cache invalidations. Public CloudFront viewing is still unlisted, not authenticated.

04

Operational debugging

Diagnosed S3 access denial, invalidation permissions, DNS resolver mismatch, HLS CORS behavior and stale HTML deployment paths.

Measured playlist variants

2160p  · 3840×2160 · 22.26 Mbps avg (41.96 peak)
1080p  · 1920×1080 ·  7.53 Mbps avg (14.87 peak)
 540p  ·  960×540  ·  2.46 Mbps avg ( 5.74 peak)
 360p  ·  640×360  ·  1.06 Mbps avg ( 2.15 peak)

Values are playlist metadata, not a measurement of a viewer's throughput. A screenshot of selecting 2160p does not independently prove decoded 4K frames or an uninterrupted full-film watch.

Verification and limitations

This is a single-video learning beta, not a public streaming SaaS. Private footage, viewer URLs, AWS account details and certificate DNS tokens are intentionally excluded.

Read complete AWS deployment, DNS, IAM, HLS and troubleshooting runbook →

Read GoDaddy + CloudFront domain lab →