---
title: "Comment by Ridam Darji on \"The AWS Autopsy | Case #02 — IAM Privilege Escalation - Uber\" | Hashnode"
description: "Editor's Note: A reader correctly pointed out that no public source confirms Uber's exact IAM policy configuration. The lab demonstrates the documented IAM Priv"
url: "https://hashnode.com/posts/the-aws-autopsy-case-02-iam-privilege-escalation-uber/6a04ba82a0c1540277618a8e/comment/6a05f385baf09db7a61737e1"
---

[Discussion](https://hashnode.com/posts/the-aws-autopsy-case-02-iam-privilege-escalation-uber/6a04ba82a0c1540277618a8e)

Comment [The AWS Autopsy | Case #02 — IAM Privilege Escalation - Uber](https://hashnode.com/posts/the-aws-autopsy-case-02-iam-privilege-escalation-uber/6a04ba82a0c1540277618a8e)

[Ridam Darji](https://hashnode.com/@w1tn3sss)

[May 14](https://hashnode.com/posts/the-aws-autopsy-case-02-iam-privilege-escalation-uber/6a04ba82a0c1540277618a8e/comment/6a05f385baf09db7a61737e1)

Editor's Note: A reader correctly pointed out that no public source confirms Uber's exact IAM policy configuration. The lab demonstrates the documented IAM PrivEsc vector that becomes exploitable once AWS admin keys are obtained, not a Uber-specific claim.