1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.S T G 3 5 1Inside S3:Lessons from exabyte-scale data lake modernizationCarl SummersHe/HimPrincipal Software EngineerAmazon S3He/HimSenior Specialist Solution Archite
2、ctData&AI,WWSORan Pergamin 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.TodayMt Everest8,849mNext year 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Not just logs 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Three critical questions fo
3、r your organizationTime allocation analysisAre your engineers spending more time finding data than analyzing it?Incident resolution speedHow much faster could you resolve issues with better log insights?Untapped business intelligence 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved
4、.Three critical questions for your organizationTime allocation analysisAre your engineers spending more time finding data than analyzing it?Incident resolution speedHow much faster could you resolve issues with better log insights?Untapped business intelligenceWhat business questions remain unanswer
5、ed because the data is too difficult to access?2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.“The chances of that happening are,like,one in a billion.Carl Summers,Software Developer(SDE)II,Oct-ish 2013 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.My first f
6、eature Config config=bucketConfigService.fetch(bucketName);2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.My first lesson in scaletry Config config=bucketConfigService.fetch(bucketName);catch(SuperDuperUnlikelyException e)throw new InternalError500(e);2025,Amazon Web Services,Inc