AWS re:Invent 2023 - Dive deep on Amazon S3 (STG314)

[@Kane0123]

Imagine being part of a single team for 10years and still having that kind of joy and excitement for the product... goals.

[@audioplatform6299]

Well, if the Amazon stock had not gone up and still has that kind of joy, that's special

[@GyeongSuGim-e3b]

Easy-to-understand the core concepts of S3 mitigations against the real world threats. Thank you both for providing such a good presentation.

[@known_fellow5916]

One of the best session of this year's re:invent ! It's captivating to observe the intricate architecture marvels that underlie a seemingly simple storage service (S3) !

[@vgsuresh]

very useful session and how the things are handled at scale.

[@wayfarerluka]

Why they are partitioning based on bucket name instead of using its hash so that customer wouldn’t need to worry about scaling factor (which stems from implementation detail) while naming buckets?

[@awssupport]

Great question! This doc may clear things up: go.aws/3x1RF85. If not, our community of experts in re:Post may be able to share some insight: go.aws/aws-repost. You can also reach out to our S3 team via this contact form: go.aws/4aiJgvi. 👈 ^LG

[@giteshkhanna2633]

Nice talk!

[@jairjosafath9693]

amazing content. Nice to know the technology behind 11 nines durability. is it safe to say S3 is a superpowered block storage underneath? since the objects are seperated in smaller chunks?

[@awssupport]

That's a great question! There are a few key differences between block storage & object storage, but these links can provide a more in-depth look into each storage type: go.aws/47X9na4 & go.aws/3RdUvh0. I'd also encourage looking through our Amazon S3 page: go.aws/3R93MXD, or reaching out to our S3 team via this form for any other questions: go.aws/47UHsaK. ^RM

[@ds12v123]

Nice information