| 1 | |  | AWS CloudFront in 3 Steps |
| | | |
| 2 | | | 1. Prepare Your Content |
| Developer | Not Started | |
| 3 | | | Read the AWS CloudFront documentation (click on paper clip to view) |
| Developer | Not Started | Check for most recent updates at: http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=211 |
| 4 | | | Enable the CloudFront Service for your AWS account(s) |
| Developer | Not Started | http://aws.amazon.com/cloudfront/ |
| 5 | | | Create your S3 bucket for your CloudFront content |
| Developer | Not Started | Because this and the next step only need to happen once, using an S3 tool like the Firefox add-in S3Fox can be easier than writing code to the API. Keep an eye out for updates in the AWS Developer Community: http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=173
S3Fox: http://www.suchisoft.com/ext/s3fox.php |
| 6 | | | Prepare your CloudFront content and upload process |
| Developer | Not Started | Depending on your content, you might want to hook up your application or website build process to automatically upload your content. |
| 7 | | | Upload your content to the CloudFront bucket |
| Developer | Not Started | |
| 8 | | | 2. Enable the CloudFront distribution on the Bucket |
| Developer | Not Started | |
| 9 | | | If you would like a friendly name for your CloudFront url, setup a DNS CNAME to alias the distribution name |
| Developer | Not Started | Typically you will need to setup this using the tools provided by your domain host. |
| 10 | | | 3. Create links in your website/application to point to your CloudFront location |
| Developer | Not Started | |
| 11 | | | Test downloading items from CloudFront Url |
| Developer | Not Started | |
| 12 | | | Access your website or application and enjoy the speed |
| Developer | Not Started | |
| 13 | | | Technical considerations |
| | | |
| 14 | | | Optimizing the content |
| Developer | Not Started | |
| 15 | | | Set cache control headers on your files to ensure the edge caches the files appropriately |
| Developer | Not Started | An example would be to set the header "Cache-control: max-age=2592000, public" |
| 16 | | | Gzip encode html, javascript, css and other appropriate content |
| Developer | Not Started | If you need to support older browsers that do not support gzip encoding, then you might need to upload both a normal and gzip encoded file and conditionally direct users to the appropriate one. |
| 17 | | | Enabling your website or application to use CloudFront |
| Developer | Not Started | |
| 18 | | | Ensure that you have unique file names for your CloudFront content so that when you change a file, it will have a new name |
| Developer | Not Started | |
| 19 | | | Conditionally use the service for certain users/browser types |
| Developer | Not Started | |
| 20 | | | IE 6 pre SP1 does not always handle Gzip encoded content well |
| Developer | Not Started | |
| 21 | | | If your website/app runs over HTTPS don't send IE users to the CloudFront content on HTTPS pages to avoid the mixed content security warnings |
| Developer | Not Started | |