当前位置:首页 > 报告详情

保障事件驱动架构的安全:从同步到异步安全.pdf

上传人: 明**** 编号:1013596 2025-12-21 23页 273.89KB

1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.S P S 3 2 3Securing Event-Driven Architectures:Moving from Sync to Async SecuritySergio Bilbao LpezSenior Cloud Infrastructure ArchitectHe/HimIgor DAstolfoDevOps Arc

2、hitectHe/Him 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Synchronous vs Asynchronous(context on async)The journey of“”(the story)Number of providers messages anomalyNumber of internal messages anomalyMessage IntegrityDid we do a good job?Takeaways and recommendations 2025,Amaz

3、on Web Services,Inc.or its affiliates.All rights reserved.Synchronous vs Asynchronous 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.S Y N C H R O N O U S V S A S Y N C H R O N O U SWhy Async?Loose couplingScalabilityAsynchronous processingEvent sourcingFlexibility 2025,Amazon We

4、b Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.The journey of 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.T H E J O U R N E Y O F N O B L E A N D M A R E.C O ME is an e-commerce web site that sells luxury

5、 itemsYou started small,but youre gaining momentum and sells are booming!With the success of the web site,performance issues start to emerge 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Evolution to asynchronous 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved

6、.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Number of providers messages anomaly 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.T H E J O U R N E Y O F N O B L E A N D M A R E.C O MPublic SecurityAPI Gateway request?Why non-allowed producer are writing mes

word格式文档无特别注明外均可编辑修改,预览文件经过压缩,下载原文更清晰!
三个皮匠报告文库所有资源均是客户上传分享,仅供网友学习交流,未经上传用户书面授权,请勿作商用。
本文讲述了电子商务网站“nobleandmare.com”在面对业务增长时,从同步架构迁移到异步架构的安全挑战和解决方案。关键点如下: 1. **异步的优势**:包括松耦合、可扩展性、异步处理、事件溯源和灵活性。 2. **迁移过程**:随着网站成功,性能问题凸显,促使进化到异步架构。 3. **安全挑战**: - **外部消息异常**:未经授权的生产者发送消息,质疑政策正确性。 - **内部消息异常**:消息数量多于预期,需控制信息访问。 - **消息完整性**:大量废弃消息和非标准消息出现。 4. **解决方案**: - **组织级控制**:实施SCP防止跨账户事件流,使用AWS组织强制执行一致的安全控制。 - **账户级控制**:遵循最小权限原则,对事件总线及目标应用限制性策略。 - **服务级控制**:特定事件模式、事件模式验证、规则审计,以及监控策略。 5. **检测策略**:使用CloudWatch指标和CloudTrail分析监测可疑行为。 文章强调了实施多层控制和安全审计的重要性,以保障异步事件驱动架构的安全性。
从同步到异步的转型" 如何应对消息异常?" 如何确保事件驱动架构安全?"
客服
商务合作
小程序
服务号
折叠