Bolstering incident response with AWS Wickr enterprise integrations
summary
Shows a working integration that pushes Amazon GuardDuty JSON findings into an AWS Wickr room via EventBridge, Amazon API Gateway, a WAF and load balancer to an EC2-hosted Docker Wickr API bot, demonstrating an actual pipeline rather than theory. Uses GuardDuty, EventBridge, API Gateway and an EC2 container; findings appear as direct messages or room posts. Notes end-to-end encryption with per-message distinct keys, multi‑client support, and a 90‑day free trial for 30 users in us‑east‑1.
AI-written summary · about
chapters (6)
- 0:00Introduction and welcome
- 1:05What is AWS Wickr
- 3:57AWS Wickr integrations and bots
- 5:21Incident response workflow demo
- 7:48Getting started with AWS Wickr
- 10:16Q&A and closing
related talks
35mThe Good, the Bad and the Ugly — one year of integrating AWS security services
32mAdvanced threat detection and response on AWS
15mSecure and scale your cloud foundations using AWS Built-in
34mLayering AWS security services to automate incident response
55mSecure your APIs the Well-Architected way from foundation to perimeter
51mInnovations in AWS detection and response services
29mAutomating Threat Detection and Remediation
35mEvent-driven Security with AWS Security Services