Use lessons learned from the field to build for security
summary
Common field mistakes and concrete fixes: enable GuardDuty everywhere and wire each finding to a CloudWatch event rule that triggers a Lambda or SNS (there are nine-line Python samples and a shell script to activate detectors across regions or a CloudFormation StackSet). Use Customer Managed KMS keys for editable key policies and remember imported key deletion is immediate (default KMS deletion has a 7‑day grace). Create a multi‑region CloudTrail to S3 with log file integrity validation, use identity federation or AWS SSO not IAM users, enforce sensitive actions with SCP Deny, and replace public SSH/RDP with Session Manager, prefix lists, Firewall Manager, and deny public S3.
AI-written summary · about
chapters (8)
related talks
01h 02mStrong security made simple: Putting all the pieces together
51mAWS Security Essentials
44mGuardrails in the Cloud
27mProactively identifying threats & protecting sensitive data in S3
29mAutomating Threat Detection and Remediation
34mWhat “Security Needs to Be Our Top Priority” Means for Aws Builders/Customers
34mSecurity best practices for End User Computing Services
51mBuilding a Cloud Security Flywheel: Lessons from the Field