Working with Amazon CloudFront for Dynamic Content Acceleration Reviews

Dileep K. · Reviewed over 9 years ago

Vignesh K. · Reviewed over 9 years ago

Paul T. · Reviewed over 9 years ago

suman j. · Reviewed over 9 years ago

Sujith N. · Reviewed over 9 years ago

Suvradip C. · Reviewed over 9 years ago

Justin L. · Reviewed over 9 years ago

shesh p. · Reviewed over 9 years ago

Amit J. · Reviewed over 9 years ago

Bharathi Kannan K. · Reviewed over 9 years ago

Marimuthu B. · Reviewed over 9 years ago

Philos H. · Reviewed over 9 years ago

Mathew A. · Reviewed over 9 years ago

Z A. · Reviewed over 9 years ago

Dan H. · Reviewed over 9 years ago

Festum Q. · Reviewed over 9 years ago

claire d. · Reviewed over 9 years ago

Rahul G. · Reviewed over 9 years ago

Do fix the typos (sunder -> under). Seemed to be some missing items like WAF. Also I think CREATE ORIGIN/Restrict Bucket Access should be set to default 'No', not 'Yes' as it then asked for a username, otherwise couldn't submit. Also should have student try a bad url to see that the 404 file actually works.

Mark M. · Reviewed over 9 years ago

Sebastin Jayaraj T. · Reviewed over 9 years ago

chris v. · Reviewed over 9 years ago

There were some typos in the PDF instructions. Cache behavior in CloudFront from typing /no_page_found.html was not as expected - after waiting for the distribution to be 'deployed', it did not forward me to the Custom404ErrorPage.html in the S3 bucket but if I typed domainname.cloudfront.net/Custom404ErrorPage.html, it brought me to the page served by s3.

Fabian L. · Reviewed over 9 years ago

Syed Farooq A. · Reviewed over 9 years ago

Michael F. · Reviewed over 9 years ago

San M. · Reviewed over 9 years ago