| AWS re:Inforce 2024 - Establishing a data perimeter on AWS, featuring Capital One (IAM305) |
2024-06-18 |
| AWS re:Inforce 2024 - Securing Amazon Q Business custom apps with AWS IAM Identity Center (IAM324) |
2024-06-14 |
| AWS re:Inforce 2024 - Traffic safety: Auditing and enforcing IAM best practices (IAM303-S) |
2024-06-14 |
| AWS re:Inforce 2024 - Refine unused access confidently with IAM Access Analyzer (IAM202-NEW) |
2024-06-14 |
| AWS re:Inforce 2024 - Proving the correctness of AWS authorization (IAM401) |
2024-06-14 |
| AWS re:Inforce 2024 - Managing customer identities with Amazon Cognito (IAM221) |
2024-06-14 |
| AWS re:Inforce 2024 - How PicPay achieved temporary elevated access control on AWS (IAM323) |
2024-06-14 |
| AWS re:Inforce 2024 - Amazon S3 presigned URL security (IAM321) |
2024-06-14 |
| AWS re:Inforce 2024 - Boosting security for devs & their apps with identity security (IAM222-S) |
2024-06-13 |
| AWS re:Inforce 2024 - Using AWS SCPs to achieve least privilege while supporting devs (IAM325-S) |
2024-06-13 |
| AWS re:Inforce 2024 - IAM policy power hour (IAM304) |
2024-06-12 |
| AWS re:Inforce 2024 - Staying ahead of threat actors with Amazon Cognito, featuring Dynata (IAM302) |
2024-06-12 |
| AWS re:Inforce 2024 - Access management: Customer use of Cedar policy & Verified Permissions IAM201 |
2024-06-12 |
| AWS re:Inforce 2024 - Making cloud security more human, featuring Block (IAM322) |
2024-06-12 |
| AWS re:Inforce 2024 - Users and their data: Modern access and audit patterns on AWS (IAM301) |
2024-06-11 |