What “Security Needs to Be Our Top Priority” Means for Aws Builders/Customers
summary
Claims that leaked AWS keys are exploited under one minute and shows concrete defenses: enable Trusted Advisor checks and weekly alerts, run Amazon Inspector for images and Lambda, ingest findings into AWS Security Hub and automate remediation via EventBridge/Lambda. Demonstrations cover eliminating hardcoded credentials with IAM roles and IAM Roles Anywhere, closing public S3 and fronting with CloudFront, and using AWS Shield Advanced and the Well-Architected Framework to enforce and audit controls.
AI-written summary · about
chapters (18)
- 0:00Security as top priority
- 1:26Exposed API keys impact
- 2:55Shared responsibility model
- 4:43Security services for builders
- 7:49Security team challenges
- 8:30Centralizing findings with Security Hub
- 11:26Securing public endpoints
- 13:19Strict S3 bucket policies
- 16:37Avoid hardcoded credentials
- 19:34Closing attack vectors
- 21:49DDoS protection with Shield Advanced
- 22:51Managing PII compliance
- 24:37Freezing dev for security
- 26:20SAP secures 6,000 accounts
- 27:47Well-Architected security
- 29:12Mechanisms over intentions
- 30:16Key takeaways
- 31:40Q&A
related talks
53mAchieving End-to-end Security on AWS
18mHow AWS Partners use observability to strengthen customer security
27mIntroduction to AWS Security
01h 08mKeynote
27mIntroduction to AWS Security
51mAWS Security Essentials
25mUse lessons learned from the field to build for security
27mProactively identifying threats & protecting sensitive data in S3