I've been attempting to get cloudfront signed cookies setup for a site to make getting HLS manifest segment files easier to authenticate. Setting up the cloudfront origin and code in a live environment seems simple enough looking at resources like
- https://mnm.at/markus/2015/04/05/serving-private-content-through-cloudfront-using-signed-cookies/
- http://www.spacevatican.org/2015/5/1/using-cloudfront-signed-cookies/
What I'm trying to figure out is if it's possible to to have this working in a local environment (localhost) prior to deploying the initial solution. Cloudfront itself will forward to the live origin which will set the cookies for cloudfront and continue on as normal, but since the code isn't live this will not work until deployed.
Seems like a chicken and egg problem here where I need it live to use it, but can not test it (with code or manually) without it deployed.
Any thoughts here?
The parameter origin name cannot be an IP address... but yes, that's essentially what's involved. I use an exposed HAProxy server with multiple hostnames pointing to its single external address, to selectively route HTTP requests inside based on the incoming host header and source IP rules, rather than directly opening internal machines to the 'net. I also have an Internet-exposed pre-launch QA/test environment, identical to production except the hostnames pointing to it. - Michael - sqlbot