Re:Things you wish you didn't need to know about S3
by teitoklien on Friday May 31, 2024 @01:46AM
(#40531877)
Most folks use S3 as a source for AWS cloudfront for serving content
You can even use cloudfront signed cookies to give specific users cdn access to only specific content owned by them on S3. How cool is that.
Re:Things you wish you didn't need to know about S3
by WatchDog on Friday May 31, 2024 @01:45AM
(#40531874)
Typically you would use cloudfront with S3 if you want to use it for serving web assets.
It will cache frequently accessed assets, and in addition to reducing latency may reduce cost quite a bit.
Re:Things you wish you didn't need to know about S3
by lulznews on Friday May 31, 2024 @01:41AM
(#40531853)
Pretty much everyone knows this …
Re:Things you wish you didn't need to know about S3
by metadat on Friday May 31, 2024 @01:37AM
(#40531837)
Put a memcached instance in front and you're good.
Re:Things you wish you didn't need to know about S3
by mcqueenjordan on Friday May 31, 2024 @04:44AM
(#40532739)
s3 is not optimized to directly serve websites, but to durably store and retrieve ~unlimited data.
Re:Things you wish you didn't need to know about S3
by weird-eye-issue on Friday May 31, 2024 @09:09AM
(#40534698)
This has been well known for over a decade
Many people think you can just host the resources for your websites, such as images or fonts, straight on S3. But that can make for a shitty experience:
> applications can achieve consistent small object latencies (and first-byte-out latencies for larger objects) of roughly 100–200 milliseconds.
From: https://docs.aws.amazon.com/AmazonS3/latest/userguide/optimi...