Cloud upgrade: Modern TLS encryption for all AWS service connections
summary
AWS updates all public API endpoints to require TLS 1.2+ and removes TLS 1.0/1.1 across ~9,000 endpoints for 200 services, detecting 185,000 accounts still using old protocols. A serverless big‑data pipeline (CloudTrail → S3 → Glue → Athena) processes about 800 billion records per hour to find impacts and drive notifications. TLS 1.3 rollout uses s2n, ELB controls, CloudWatch and sidelining to isolate failures; about 80% of connections already negotiate 1.3. PQC work ships hybrid Kyber key exchange in KMS/ACM/Secrets Manager and CloudFront supports QUIC/HTTP3.
AI-written summary · about
chapters (8)
- 0:00Introduction and overview
- 1:05TLS fundamentals explained
- 7:52Deprecating TLS 1.0 and 1.1
- 15:26Enabling TLS 1.3 benefits
- 20:24TLS 1.3 rollout challenges
- 33:25Future of TLS post-quantum crypto
- 53:47HTTP/3 and QUIC innovations
- 59:46Q&A and closing
related talks
58mUsing AWS data protection services for innovation and automation
01h 00mBehind the scenes: AWS investments in security innovation
10mWhat's New on AWS Serverless for 2022!
15mSecuring Cloud Native Infra for the Post-Quantum Era
32mWhat’s new with Amazon S3
45mSecurity Lessons Learned Moving a Bank 100% in the Cloud
01h 03mContinuous Security in the Cloud
28mSecuring Multi-Cloud and Hybrid Environments