I have created a S3 bucket, uploaded a video, created a streaming distribution in CloudFront. Tested it with a static HTML player and it works. I have created a keypair through the account settings. I have the private key file sitting on my desktop at the moment. That’s where I am.
My aim is to get to a point where my Django/Python site creates secure URLs and people can’t access the videos unless they’ve come from one of my pages. The problem is I’m allergic to the way Amazon have laid things out and I’m just getting more and more confused.
I realise this isn’t going to be the best question on StackOverflow but I’m certain I can’t be the only fool out here that can’t make heads or tails out of how to set up a secure CloudFront/S3 situation. I would really appreciate your help and am willing (once two days has passed) give a 500pt bounty to the best answer.
I have several questions that, once answered, should fit into one explanation of how to accomplish what I’m after:
-
In the documentation (there’s an example in the next point) there’s lots of XML lying around telling me I need to
POSTthings to various places. Is there an online console for doing this? Or do I literally have to force this up via cURL (et al)? -
How do I create a Origin Access Identity for CloudFront and bind it to my distribution? I’ve read this document but, per the first point, don’t know what to do with it. How does my keypair fit into this?
-
Once that’s done, how do I limit the S3 bucket to only allow people to download things through that identity? If this is another XML jobby rather than clicking around the web UI, please tell me where and how I’m supposed to get this into my account.
-
In Python, what’s the easiest way of generating an expiring URL for a file. I have
botoinstalled but I don’t see how to get a file from a streaming distribution. -
Are there are any applications or scripts that can take the difficulty of setting this garb up? I use Ubuntu (Linux) but I have XP in a VM if it’s Windows-only. I’ve already looked at CloudBerry S3 Explorer Pro – but it makes about as much sense as the online UI.
You’re right, it takes a lot of API work to get this set up. I hope they get it in the AWS Console soon!
UPDATE: I have submitted this code to boto – as of boto v2.1 (released 2011-10-27) this gets much easier. For boto < 2.1, use the instructions here. For boto 2.1 or greater, get the updated instructions on my blog: http://www.secretmike.com/2011/10/aws-cloudfront-secure-streaming.html Once boto v2.1 gets packaged by more distros I’ll update the answer here.
To accomplish what you want you need to perform the following steps which I will detail below:
1 – Create Bucket and upload object
The easiest way to do this is through the AWS Console but for completeness I’ll show how using boto. Boto code is shown here:
2 – Create a Cloudfront “Origin Access Identity”
For now, this step can only be performed using the API. Boto code is here:
3 – Modify the ACLs on your objects
Now that we’ve got our special S3 user account (the S3CanonicalUserId we created above) we need to give it access to our s3 objects. We can do this easily using the AWS Console by opening the object’s (not the bucket’s!) Permissions tab, click the “Add more permissions” button, and pasting the very long S3CanonicalUserId we got above into the “Grantee” field of a new. Make sure you give the new permission “Open/Download” rights.
You can also do this in code using the following boto script:
4 – Create a cloudfront distribution
Note that custom origins and private distributions are not fully supported in boto until version 2.0 which has not been formally released at time of writing. The code below pulls out some code from the boto 2.0 branch and hacks it together to get it going but it’s not pretty. The 2.0 branch handles this much more elegantly – definitely use that if possible!
5 – Test that you can download objects from cloudfront but not from s3
You should now be able to verify:
The tests will have to be adjusted to work with your stream player, but the basic idea is that only the basic cloudfront url should work.
6 – Create a keypair for CloudFront
I think the only way to do this is through Amazon’s web site. Go into your AWS “Account” page and click on the “Security Credentials” link. Click on the “Key Pairs” tab then click “Create a New Key Pair”. This will generate a new key pair for you and automatically download a private key file (pk-xxxxxxxxx.pem). Keep the key file safe and private. Also note down the “Key Pair ID” from amazon as we will need it in the next step.
7 – Generate some URLs in Python
As of boto version 2.0 there does not seem to be any support for generating signed CloudFront URLs. Python does not include RSA encryption routines in the standard library so we will have to use an additional library. I’ve used M2Crypto in this example.
For a non-streaming distribution, you must use the full cloudfront URL as the resource, however for streaming we only use the object name of the video file. See the code below for a full example of generating a URL which only lasts for 5 minutes.
This code is based loosely on the PHP example code provided by Amazon in the CloudFront documentation.
8 – Try out the URLs
Hopefully you should now have a working URL which looks something like this:
Put this into your js and you should have something which looks like this (from the PHP example in Amazon’s CloudFront documentation):
Summary
As you can see, not very easy! boto v2 will help a lot setting up the distribution. I will find out if it’s possible to get some URL generation code in there as well to improve this great library!