Working with Amazon CloudFront for Dynamic Content Acceleration Reviews
4069 reviews
Sungryol P. · Reviewed almost 8 years ago
Vijay S. · Reviewed almost 8 years ago
CHAITANYA LATHA K. · Reviewed almost 8 years ago
Dileep K. · Reviewed almost 8 years ago
Vignesh K. · Reviewed almost 8 years ago
Paul T. · Reviewed almost 8 years ago
suman j. · Reviewed almost 8 years ago
Sujith N. · Reviewed almost 8 years ago
Suvradip C. · Reviewed almost 8 years ago
Justin L. · Reviewed almost 8 years ago
shesh p. · Reviewed almost 8 years ago
Amit J. · Reviewed almost 8 years ago
Bharathi Kannan K. · Reviewed almost 8 years ago
Marimuthu B. · Reviewed almost 8 years ago
Philos H. · Reviewed almost 8 years ago
Mathew A. · Reviewed almost 8 years ago
Z A. · Reviewed almost 8 years ago
Dan H. · Reviewed almost 8 years ago
Festum Q. · Reviewed almost 8 years ago
claire d. · Reviewed almost 8 years ago
Rahul G. · Reviewed almost 8 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 almost 8 years ago
Sebastin Jayaraj T. · Reviewed almost 8 years ago
chris v. · Reviewed almost 8 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 almost 8 years ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.