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.

1. #reinvent

3. Dynamic
Static

4. Static content is the objects
on your website that don’t
change from user to user
• Images
• Media
• CSS
• JavaScript

5. Dynamic content is the
interactive or personalized
portion of a website, created
on-the-fly for each end user
• Customer names
• News & Weather
• Sports
• Stocks
• Travel

6. Deliver dynamic content from Use solutions from traditional
your own origin servers content delivery networks
• Slow • Expensive
• Hard to scale • Complicated
• Single points of failure • Proprietary code
• Increased load to the origin

7. Dynamic Content with CloudFront
Simple DIY configuration with web console
Simple to Use No consultants to hire
No proprietary languages to learn
Designed to work with origins in Amazon EC2
AWS Integration Connections to AWS regions closely monitored
Standard AWS resources (like AWS CloudFormation)
No additional charges or set up fees
Low Cost Pay only for requests and data transfer

8. How It Works
User to CloudFront Dynamic Content
Routing based on lowest latency
TCP Optimizations
Persistent 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

9. Europe
Amsterdam (2)
Dublin
North America Frankfurt (2)
Ashburn, VA (2) London (2)
Dallas, TX (2) Asia
Madrid
Jacksonville, FL Hong Kong
Milan
Los Angeles, CA (2) Osaka
Paris (2)
Miami, FL Singapore (2)
Stockholm
Newark, NJ Sydney
New York, NY (3) Tokyo (2)
Palo Alto, CA
Seattle, WA South America
San Jose, CA Sao Paulo
South Bend, IN
St. Louis, MO

10. 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.

13. 1. Connection optimizations
2. Multiple cache behaviors
3. Multiple origin servers
4. Query string parameters and
cookie support

14. Origin to CloudFront CloudFront to User
• Persistent connections • Routing optimizations
• Collapsed forwarding • TCP optimizations
• AWS monitored paths • Persistent connections

15. Separate static and dynamic
content (S3 versus ELB)
Organize your content into
different buckets or origins
Incorporate different back-end
services
All using a single domain name

16. • Select a different origin
Based on pattern • Require SSL
matching of each • Use private content
request, you can: • Change the minimum TTL
• Cache cookies or query strings

17. Ways to personalize and
customize pages and sites
Whitelist of cookies and query
strings to forward to your origin
Cookies and query strings you
specify are part of cache

30. www.aws.amazon.com/cloudfront/dynamic-content
http://aws.amazon.com/cloudfront

31. www.aws.amazon.com/cloudfront
www.aws.amazon.com/cloudfront
www.aws.amazon.com/cloudfront
www.aws.amazon.com/cloudfront/dynamic-content
www.aws.amazon.com/cloudfront

32. #reinvent
We are sincerely eager to
hear your feedback on this
presentation and on re:Invent.
Please fill out an evaluation
form when you have a
chance.