While serving content from Azure Blob storage directly is feasible, it may not be the best fit in all scenarios. In this course, Microsoft Azure Developer: Implementing CDNs for Storage, you will gain the ability to integrate Azure CDN with Azure Blob Storage containers. First, you will learn how Azure CDN works and what scenarios it excels at. Next, you will discover how to configure Azure CDN on top of a blob storage container using common Azure tools and SDKs. Finally, you will explore how to maintain storage security with SAS token authentication. When you’re finished with this course, you will have the skills and knowledge of Azure CDN needed to effectively enable serving content from your Azure Blob Storage account.
Course Overview Hi everyone, my name is Kamran Ayub, and welcome to my course, Implementing CDNs for Storage, part of the Microsoft Azure Developer course catalog, here at Pluralsight. I'm a technologist, speaker, and, of course, Pluralsight author based in the Midwest, and I've been working with Azure throughout most of my career, so I'm excited to bring you this course. Azure's content delivery network, CDN, product provides a high-performance, scalable edge network to serve your content efficiently, and even create advanced rules to manage user access. I'm going to be talking about how to implement Azure CDN with Azure Blob service, and since I love being hands on, there's going to be plenty of demos. We'll learn how to integrate Azure CND with Azure Storage and cover topics like key CDN concepts and billing scenarios; automation with Azure tools and SDKs; authenticating with shared access signature, or SAS, tokens; and exploring the static website feature. By the end of this course, you'll be able to implement and develop solutions that integrate Azure CDN with Azure Storage, both in public and private authentication scenarios. Before beginning the course, you should be familiar with how Azure works and how to create and manage Azure Storage accounts, but you don't need to be familiar with Azure CDN. I hope you'll join me on this journey to learn about Azure CDN with the Implementing CDNs for Storage course at Pluralsight.
Azure CDN and Storage Concepts Hi, I'm Kamran Ayub, and let me welcome you to my course on implementing CDNs for Storage, part of the Microsoft Azure Developer course catalog here at Pluralsight. As a longtime Microsoft Azure developer myself, I'm really excited to cover this topic and help you enable serving content using Azure CDN integrated with Azure Storage. As this is our first module, we'll cover some key concepts around Azure CDN and what benefits it brings when used with Azure storage. I will also walk through a pricing scenario with example numbers, as well as where to find costs related to Azure CDN and Storage in your Azure account that should help to solidify your understanding of how your bill might be impacted by using these two services together. And finally, we'll take a closer look at the example static Blob files stored in Azure Storage that we'll use as a demo for the rest of the course.
Implementing Azure CDN with Storage It's time we learn how to enable Azure CDN on our Azure Storage account. This module is organized so that you can jump to a specific type of automation tool if you need to, or you can also just watch them in order if you haven't used them before. I don't assume you have the tools installed or how they work, so I'll explain each one at the start of each demo, and we'll walk through them together. By the end of this module, you'll learn how easy it is to enable Azure CDN on your Storage accounts and what cross-platform tools are available to help manage CDN resources. At the end, we'll also take a look at how performance compares against serving our demo static site with Blob Storage. All the demo scripts I present are available in the exercise files for this course, along with some additional tips and tricks when using the tools. Before we jump into any of these demos, I wanted to explain the terms and resources you'll see. First, all Azure resources are organized under a subscription, and an account could have multiple subscriptions. In many of these demos, you'll see we need to provide a subscription ID before we can create resources. Then Azure CDN is organized by a logical grouping of CDN endpoints called a profile. Within a profile, there are CDN endpoints, which is the public-facing URL and configuration for your CDN. Related to endpoints, but also a separate entity, are origins, which represent the backing origin server configuration, such as Blob Storage a custom origin. Both endpoints and origins have configuration options, and endpoints are explicitly linked to origins. This object model is good to understand when trying to automate Azure CDN since you need to know in which order to create these resources. Alright, time for the demos.
Storage Security with Azure CDN So far, we've only configured Azure CDN to work with a public Blob container, but in many scenarios, you'll want to use Azure CDN with a private Storage account. Azure Storage accounts can be protected using special security tokens called shared access signatures, or SAS tokens, and we'll spend most of the time covering how these can be used in conjunction with Azure CDN. In this module, we'll first cover how SAS tokens work with Azure CDN and why you'd want to use them for CDN scenarios. Then we'll move into covering three authentication scenarios using SAS tokens, each one in order of increasing complexity, which will involve configuring both the standard Azure CDN sku and the premium sku using the advanced Rules Engine feature. If you've never configured SAS token authentication with Azure CDN before, I'd highly recommend watching all the SAS videos in order, rather than starting in the middle or at the most advanced option. As we'll discuss, each one can be useful in different scenarios that you'll want to understand. Finally, I'll cover the static websites feature in Azure Storage that offers a simple alternative to SAS token authentication using a read-only Blob endpoint, which might be suitable for basic website hosting scenarios.