Using AWS S3 vs Cloudfront

Since the heroku file system is ephemeral, I plan to use AWS for static resources for my django project on heroku

I see two conflicting articles that advise using AWS S3. It says use S3

https://devcenter.heroku.com/articles/s3

While another one below says that S3 has flaws and use Cloudfront CDN instead

https://devcenter.heroku.com/articles/using-amazon-cloudfront-cdn

Many developers use the Amazons S3 service to service static assets that were previously downloaded, either manually or by some form of the build process. Although this works, it is not recommended since S3 was designed as a file storage service, and not for optimal file delivery under load. Therefore, maintaining static assets with S3 is not recommended.

+4
source share
3 answers

Amazon CloudFront - (CDN), - Amazon, S3, .

CloudFront ( ). , ( AWS 35 , ), , S3, .

, , CloudFront else, , CloudFront, S3 ( S3: , , - , , ..)

Amazon S3 CloudFront

+6

- CloudFront Whitenoise. Heroku, CloudFront CDN , .

Whitenoise .

http://whitenoise.evans.io/en/latest/ .

( , Whitenoise , , , - S3 . CF.)

+3

, .

CloudFront CDN, , . , , .

CloudFront . S3 EC2. S3 CloudFront. CloudFront S3 .

, .

, , , .

+2

All Articles