Content Delivery Using Amazon CloudFront - AWS Presentation - John Mancuso
•
17 j'aime•6,719 vues
CloudFront is Amazon's content delivery network (CDN) that caches copies of content across a global network of edge servers to improve performance and reduce latency. It uses a distribution configuration to determine how to route requests for content to the optimal edge location. Origins specify the source of the content. CloudFront delivers content through its edge locations, improving load times, providing high bandwidth, and ensuring availability. Many companies use CloudFront to deliver media, software downloads, web assets and even dynamic content through features like cache behaviors and multiple origins. Getting started is self-service through the AWS Management Console or APIs.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Content Delivery Using Amazon CloudFront - AWS Presentation - John Mancuso
Similaire à Content Delivery Using Amazon CloudFront - AWS Presentation - John Mancuso (20)
Plus de Amazon Web Services
Plus de Amazon Web Services (20)
Dernier
Dernier (20)
Content Delivery Using Amazon CloudFront - AWS Presentation - John Mancuso
- 1. Content Delivery Using Amazon CloudFront John Mancuso jman@amazon.com
- 2. Highlights of what we’ve covered so far • What the base AWS storage offerings are • How to get data into AWS using secure and efficient tools and methodologies • How to make sure that the data that you’ve stored remains secure • How to operate on & transform your data once it’s in AWS
- 3. Agenda • Define the term CDN • Introduce CloudFront • Illustrate how CloudFront operates • Review common Use Cases for CloudFront • Walk through some customer Case Studies
- 4. What is a CDN? • A CDN (content delivery network) uses a network of geographically dispersed servers (edge locations or POPs) to cache copies of content close to end users, lowering latency when they download or stream objects.
- 5. What is a CDN? • A CDN (content delivery network) uses a network of geographically dispersed servers (edge locations or POPs) to cache copies of content close to end users, lowering latency when they download or stream objects.
- 6. Two Key CloudFront Terms • Distribution – Set of rules that controls how CloudFront will access the content you want to deliver – Output = Domain Name • Origin – Source of your content
- 7. Features of CloudFront • Low latency. Improves media load times. • High bandwidth. Enables high bit rate HD video and other media applications. • Redundant. Eliminates single points of failure. • Scalable. Ensure great experience as number of end users grows. • Global. Worldwide network provides great experience regardless of geography. • Cost-effective. Pay as you go model provides flexibility for your business.
- 8. CloudFront’s global presence Europe Amsterdam North America Dublin Ashburn, VA (2) Frankfurt (2) Dallas, TX London (2) Jacksonville, FL Milan Asia Los Angeles, CA (2) Paris Hong Kong Miami, FL Stockholm Osaka Newark, NJ Singapore (2) New York, NY (2) Tokyo Palo Alto, CA Seattle, WA San Jose, CA South America South Bend, IN Sao Paulo St. Louis, MO 8
- 9. How CloudFront Works: Non-Cached Object If content not cached – object Request routed to most requested from origin CloudFront optimal edge location S3 bucket or Edge custom origin Locations with content 2 1 End-user requests content Cached copies of objects 3 4 Data transfer of content to Data transfer of cached content CloudFront edge location to cache to end user (if cached) 9
- 10. How CloudFront Works: Cached Object Request routed to most CloudFront optimal edge location S3 bucket or Edge custom origin Locations End-user requests content with content 1 Cached copies of objects 2 Data transfer of cached content to end user (if cached) 10
- 11. When can CloudFront help you? • Static Content Use Cases: – Media Delivery (Video & Audio) – Software Download – Web Site Assets (Images, CSS, JS) • Dynamic Content Use Cases: – News – Social media – Weather – Advertising • Live Streaming – Sporting Events – Company Meetings
- 12. Dynamic Content • Multiple Cache Behaviors • Multiple Origin Servers • Minimum Expiration Period • Query String Parameters 12
- 15. Who’s using CloudFront and how are they using it?
- 17. Earth Networks “With CloudFront‟s strong performance, ease of use and flexibility, our team can use the API or the Console to quickly make changes to our CDN configuration and see the updates within minutes. And with the low cost of delivering dynamic content using CloudFront, we expect to see significant cost savings as well.” Andy Rosenbaum, Development Manager 17
- 18. Linden Labs (Second Life) Second Life, or Linden Lab, uses Amazon S3 to store downloads used in the Second Life world and CloudFront to distribute them. “CloudFront has significantly reduced the time it takes for our Residents to download our Viewer, wherever they are,” said Linden Lab‟s Bryan O‟Sullivan. “The process for getting up and running with CloudFront was simple and straightforward, and took just a few minutes.” 18
- 19. PBS PBS Interactive says it has experienced fifty percent fewer errors in its video streaming performance using CloudFront compared to its previous CDN. “We are extremely pleased with the performance and ease of use that CloudFront offers for streaming videos to different devices. With fewer errors, CloudFront delivers a great experience to our viewers, and that‟s very important for the success of our business…..using Amazon CloudFront is so simple and reliable that the team doesn‟t have to think about it. It all just works, freeing us to focus on building cool applications.”
- 20. Envoy Media Group Envoy Media Group was able to reduce costs by ~20% off costs using CloudFront. “Our costs have been reduced by approximately 20%. We no longer have to pay for locker rental and power, our man hour costs have dramatically decreased, and our bandwidth costs are lower….One of the key reasons Envoy moved to AWS was the ability to „pay as you go.‟” 20
- 21. 21
- 22. Getting Started • http://aws.amazon.com/cloudfront • Self service signup and configuration anytime, from anywhere. • AWS Management Console to create and manage CloudFront distributions. • Programmatic APIs for integration into your own systems and workflow. 22
- 23. Thank you! jman@amazon.com http://aws.amazon.com/cloudfront 23
Notes de l'éditeur
- We spent the better part of the day talking about: <read bullets from above>For some of you the next question you have might be “So now that I know how to store my content in the Cloud, how do I get it to my customers?”
- If that’s the question on your mind, then you’ve come to the right place!For the remainder of the session we are going to <read bullets>
- <read definition>That’s a mouthful, so let me highlight a few key terms before moving on.
- A CDN has servers in different geographiesThose servers store cached copies of your content& Serving content from those cached copies speeds up deliverySo maybe that sounds a little simpler now, but why wouldn’t I just serve my content directly out of EC2 or S3? Well, many customers do, but if you have a global audience having “edge caching” in place can greatly accelerate your content delivery. Even if your audience isn’t spread out around the globe, there can be significant benefit since a CDN can “absorb” load that would have otherwise been placed on your servers.
- If adding a CDN to your site sound like something you might want to do, then you’ll be thrilled by how easy it is to layer CloudFront, our CDN offering, on top of your existing infrastructure. CloudFront is completely self service. You can use the AWS management console, to create what we call a “distribution”. A distribution consists of a set of rules that dictates how CloudFront should access the content you want to distribute. The content source is typically referred to as your origin and could be EC2, S3, or any other HTTP server. Once you’ve created a distribution, you you’ll be able to distribute your content with
- If adding a CDN to your site sound like something you might want to do, then you’ll be thrilled by how easy it is to layer CloudFront, our CDN offering, on top of your existing infrastructure. CloudFront is completely self service. You can use the AWS management console, or our APIs to create what we call a “distribution”. A distribution consists of a set of rules that dictates how CloudFront should access the content you want to distribute. The content source is typically referred to as your origin and could be EC2, S3, or any other HTTP server. Once you’ve created a distribution, you you’ll be able to distribute your content with<Read slide>
- What does our global footprint look like, well, it’s constantly expanding! As of right now we have 32 edge locations around the globe. When selecting a geography to place a edge location we think about a few different things:Performance – Focusing on major internet transit hubs allows us to make sure your content is delivered as quickly as possible to your end usersWe listen to our customers – We have over 20,000 active CloudFront customers today! That’s a lot of companies giving us feedback. If you have any thoughts about where we should be, please give us that feedback.Reliability – We only go into locations where we can offer predictable performance and reliable service.
- For a quick illustration of how this works I’ll tell a story of an AWS customer in Japan. So imagine that after this presentation, one of you goes up to your room and brings up a site hosted in our Japan Region that leverages CloudFront. When you make the request, we routed you to the most optimal edge location. Likely one that is right here in NYC. That edge location will check to see if the object is in the local cache. If the object is not there, CloudFront will make a request to the origin. The object is then stored in CloudFront as well as returned to the user.
- So now, imagine that your neighbor makes the same request 2 seconds later. That request will very likely be routed to the same edge location. Cloudfront will see that the object requested is in the cache and simply serve it to the end user without having to make that long haul trip back to Japan.
- So far we’ve been talking in general terms, to get a little more specific, there are three basic categories when you might want to leverage CloudFront. Static Content, Dynamic Content & Live Streaming. The classic examples for static content are <read bullets>. Just about every web site these days has one or more of these elements. Videos for tutorials. Interactive Flash games require download of large flash files. Then there’s the normal Image CSS & JS files that are used in the construction of just about any page. In addition to the static content that people typically associate with CDN, CloudFront can also accelerate the dynamic content served up by any web server. I’m going to talk about this more in a bit, so for now I’m going to move on to live streaming.Live Streaming is another popular use case for CloudFront, especially for things like sporting events. We have simple tutorials that can show you how to setup a Live Streaming stack that could scale to 10s or 100s of thousands of users with minimal effort while affording you a great deal of control over the live streams
- Getting back to the dynamic content capabilities. These are made up of a set of features that would allow you to put CloudFront in front of your entire web site. The core features are:Multiple Caching behaviors – Meaning, you could treat static assets like .jpg files different from server generated pages like .jspfiles.Multiple Origin Servers – Meaning, you could use S3 to host the .JPG files, and EC2 to host your .JSP filesMinimal Expiration Period – Meaning, you might want some objects to stay in the cache for 1 second, or not at all. You might think well, what’s the value if there is no caching. To answer that we’ve done things like TCP & Route optimizationAnd lastly allowing for Query String parameters to be passed through to the origin.Let’s take a quick look at what this might look like for “www.mysite.com”
- Zooming into the diagram:You can direct your customers to “www.mysite.com” which resolves to a CloudFront distribution.
- The Distribution definition will say“www.mysite.com/myimage.jpg” will resolve to an s3 bucket“www.mysite.com/mypage.php” will resolve to EC2and any file in the “/ads/*” filder will be server from a custom origin outside of AWS
- We have over 60 case studies published on our web site. I’m going to dive into a couple, but if your need is slightly different than one of the ones I highlighted, please search the web site to see if
- One thing that customers love about CoudFront is that it is entirely API driven. This allows them to integrate things like the creation of distributions, or the invalidation of the cache into their code. We see an example of that here with EarthNetworkswhere they love the fact that they can make changes to CloudFront without ever having to speak to us.
- I mentioned the software download use case earlier, here’s a great example of it. Second Life stores their Viewer on S3 and distributes it using CloudFront. This has significantly reduced the time it takes for people to download their viewer and they were able to get setup quickly and easily.
- One of my favorite case studies to talk about is PBS. What makes them so interesting is that they have fully embraced AWS.For anyone who missed it, in the presiding presentation, ZenCoder showed how PBS takes their High resolution content, stores that in S3, then use ZenCoder, to transcode their video into all the different formats that they need for distribution and also store those versions in S3. They complete the story by using CloudFront to stream their videos to their end users. Embracing AWS and our partners has made the complex simple for PBS, and has had the benefits of a better experience for their viewers by lowering error rates on delivery.
- First and foremost, we have a history of price dropping, so make sure to check back frequently to make sure you are aware of current pricing.CloudFront is priced in two dimensions Data Transfer Out & Requests. As far as Data Transfer goes, you’ll see that CloudFront has a tiered pricing model that starts at 12 cents per GB for under 10TB of transfer per month and drops all the way down to 2 cents per GB for over 5 PB per month. Lastly I want to call out the last column of the chart.
- Getting Started is easy! Go to aws.amazon.com/coudfront & signup. Once you have your account, you can use the AWS Management Console to create a distribution. Once the distribution status goes “green” and you start directing traffic to CloudFront, you’ll be taking advantage of our edge network.
- I’ll be floating around and at the reception later if you have questions. If you have questions, but can’t catch me in person, please feel free to shoot me an e-mail.