#reinvent
Dynamic          Static
Static content is the objectson your website that don’tchange from user to user •   Images •   Media •   CSS •   JavaScript
Dynamic content is theinteractive or personalizedportion of a website, createdon-the-fly for each end user •   Customer na...
Deliver dynamic content from       Use solutions from traditionalyour own origin servers            content delivery netwo...
Dynamic Content with CloudFront                  Simple DIY configuration with web consoleSimple to Use     No consultants...
How It WorksUser to CloudFront                               Dynamic ContentRouting based on lowest latencyTCP Optimizatio...
Europe                      Amsterdam (2)                      DublinNorth America         Frankfurt (2)Ashburn, VA (2)   ...
Great Performance• Amazon CloudFront had to win Amazon.com’s CDN business just like any other CDN• Testing on Amazon.com s...
1. Connection optimizations2. Multiple cache behaviors3. Multiple origin servers4. Query string parameters and   cookie su...
Origin to CloudFront        CloudFront to User• Persistent connections   • Routing optimizations• Collapsed forwarding    ...
Separate static and dynamiccontent (S3 versus ELB)Organize your content intodifferent buckets or originsIncorporate differ...
•   Select a different originBased on pattern    •   Require SSLmatching of each    •   Use private contentrequest, you ca...
Ways to personalize andcustomize pages and sitesWhitelist of cookies and querystrings to forward to your originCookies and...
www.aws.amazon.com/cloudfront/dynamic-content                      http://aws.amazon.com/cloudfront
www.aws.amazon.com/cloudfront          www.aws.amazon.com/cloudfront         www.aws.amazon.com/cloudfrontwww.aws.amazon.c...
#reinvent  We are sincerely eager to hear your feedback on thispresentation and on re:Invent. Please fill out an evaluatio...
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
MED204 High Performance Content Delivery - AWS re: Invent 2012
Upcoming SlideShare
Loading in …5
×

MED204 High Performance Content Delivery - AWS re: Invent 2012

1,469 views

Published on

In this hands-on session, we demonstrate how you can use Amazon CloudFront to help architect your site to deliver both static and dynamic content (portions of your site that change for each end-user). We walk through how you can configure multiple origin servers for your Amazon CloudFront distribution providing you the flexibility to keep your content in different origin locations without the need to create multiple distributions or manage multiple domain names on your website. We also show you how you can use query string parameters to help customize your web pages for each viewer and how you can configure multiple cache behaviors for your download distribution based on URL patterns on your website.

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,469
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

MED204 High Performance Content Delivery - AWS re: Invent 2012

  1. 1. #reinvent
  2. 2. Dynamic Static
  3. 3. Static content is the objectson your website that don’tchange from user to user • Images • Media • CSS • JavaScript
  4. 4. Dynamic content is theinteractive or personalizedportion of a website, createdon-the-fly for each end user • Customer names • News & Weather • Sports • Stocks • Travel
  5. 5. Deliver dynamic content from Use solutions from traditionalyour own origin servers content delivery networks• Slow • Expensive• Hard to scale • Complicated• Single points of failure • Proprietary code• Increased load to the origin
  6. 6. Dynamic Content with CloudFront Simple DIY configuration with web consoleSimple to Use No consultants to hire No proprietary languages to learn Designed to work with origins in Amazon EC2AWS Integration Connections to AWS regions closely monitored Standard AWS resources (like AWS CloudFormation) No additional charges or set up feesLow Cost Pay only for requests and data transfer
  7. 7. How It WorksUser to CloudFront Dynamic ContentRouting based on lowest latencyTCP OptimizationsPersistent Connections Elastic Load Amazon Balancer EC2 Static Content CloudFront to Origin Separation of static and dynamic content Persistent connections to each origin Network paths monitored for performance Amazon S3
  8. 8. Europe Amsterdam (2) DublinNorth America Frankfurt (2)Ashburn, VA (2) London (2)Dallas, TX (2) Asia MadridJacksonville, FL Hong Kong MilanLos Angeles, CA (2) Osaka Paris (2)Miami, FL Singapore (2) StockholmNewark, NJ SydneyNew York, NY (3) Tokyo (2)Palo Alto, CASeattle, WA South AmericaSan Jose, CA Sao PauloSouth Bend, INSt. Louis, MO
  9. 9. Great Performance• Amazon CloudFront had to win Amazon.com’s CDN business just like any other CDN• Testing on Amazon.com shows that Amazon CloudFront is 7% faster than CDN A and 51% faster than CDN B.
  10. 10. 1. Connection optimizations2. Multiple cache behaviors3. Multiple origin servers4. Query string parameters and cookie support
  11. 11. Origin to CloudFront CloudFront to User• Persistent connections • Routing optimizations• Collapsed forwarding • TCP optimizations• AWS monitored paths • Persistent connections
  12. 12. Separate static and dynamiccontent (S3 versus ELB)Organize your content intodifferent buckets or originsIncorporate different back-endservicesAll using a single domain name
  13. 13. • Select a different originBased on pattern • Require SSLmatching of each • Use private contentrequest, you can: • Change the minimum TTL • Cache cookies or query strings
  14. 14. Ways to personalize andcustomize pages and sitesWhitelist of cookies and querystrings to forward to your originCookies and query strings youspecify are part of cache
  15. 15. www.aws.amazon.com/cloudfront/dynamic-content http://aws.amazon.com/cloudfront
  16. 16. www.aws.amazon.com/cloudfront www.aws.amazon.com/cloudfront www.aws.amazon.com/cloudfrontwww.aws.amazon.com/cloudfront/dynamic-content www.aws.amazon.com/cloudfront
  17. 17. #reinvent We are sincerely eager to hear your feedback on thispresentation and on re:Invent. Please fill out an evaluation form when you have a chance.

×