Working with Amazon CloudFront for Dynamic Content Acceleration avaliações

Sungryol P. · Revisado há about 8 years

Vijay S. · Revisado há about 8 years

CHAITANYA LATHA K. · Revisado há about 8 years

Dileep K. · Revisado há about 8 years

Vignesh K. · Revisado há about 8 years

Paul T. · Revisado há about 8 years

suman j. · Revisado há about 8 years

Sujith N. · Revisado há about 8 years

Suvradip C. · Revisado há about 8 years

Justin L. · Revisado há about 8 years

shesh p. · Revisado há about 8 years

Amit J. · Revisado há about 8 years

Bharathi Kannan K. · Revisado há about 8 years

Marimuthu B. · Revisado há about 8 years

Philos H. · Revisado há about 8 years

Mathew A. · Revisado há about 8 years

Z A. · Revisado há about 8 years

Dan H. · Revisado há about 8 years

Festum Q. · Revisado há about 8 years

claire d. · Revisado há about 8 years

Rahul G. · Revisado há about 8 years

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. · Revisado há about 8 years

Sebastin Jayaraj T. · Revisado há about 8 years

chris v. · Revisado há about 8 years

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. · Revisado há about 8 years