Setting up a CDN

Quick one to show how we handle DevOPS here at Simple Innovations.

The challenge is to set up a Content Delivery Network (CDN) in Azure so that all of the images on our new web site can be served as close to the end user as possible.

The classic DevOPS method would be to start from script and get it just right but in this case we only need to do it once so why not use the Azure portal to do it?

• If we have to rebuild from scratch after a major disaster then we have to remember how.
• Our Software as a Service offering will also use a CDN so it would be good to have that scripted  as well.

Given this I decided to use the GUI Once Then Script (GOTS) method, and yes I just made that acronym up.

This approach blends the benefits of the GUI, easy of use, hand holding, with the rigours, audit-ability and repeat-ability of the scripted method.

• Use the GUI to set up the asset, in our case the Azure Portal to set up a CDN, but don’t actually create it.
• Export the script that was used by the GUI to perform the action, in our case a PowerShell script.
• Run the script to create the asset.
• Save the script, in our case as part of the web site project.

I’m not going to run through the steps in detail as they are all standard actions and given the evergreen nature of Azure liable to change over time.

There are a few points worth pointing out though.

• Currently there is no option to host a CDN in the UK but as we will be using it for static shared content and never customer specific data that should not be a concern.
• If you want HTTPS for your CDN you have to use Verizon

So there it is we can now get back to the service and we have the configuration stored as well.