---
title: "Discussion on \"The AWS Autopsy | Case #02 — IAM Privilege Escalation - Uber\" | Hashnode"
description: "Discussion on \"The AWS Autopsy | Case #02 — IAM Privilege Escalation - Uber\". How One IAM Misconfiguration Gave an 18-Year-Old Full AWS Access at Uber\nSeries: The AWS Autopsy — Real Cloud Breaches, Dissected Difficulty: Intermediate Lab Time: ~30 minutes AWS Cost: Near zero (IA"
url: "https://hashnode.com/posts/the-aws-autopsy-case-02-iam-privilege-escalation-uber/6a04ba82a0c1540277618a8e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The AWS Autopsy | Case #02 — IAM Privilege Escalation - Uber](https://theawsautopsy.hashnode.dev/the-aws-autopsy-case-02-iam-privilege-escalation-uber?utm_source=hashnode&utm_medium=feed)

How One IAM Misconfiguration Gave an 18-Year-Old Full AWS Access at Uber Series: The AWS Autopsy — Real Cloud Breaches, Dissected Difficulty: Intermediate Lab Time: ~30 minutes AWS Cost: Near zero (IA

May 13 · 12 min read · theawsautopsy.hashnode.dev  
Read the article

## Written by

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

@w1tn3sss

  
[View profile](https://hashnode.com/@w1tn3sss)

Breaking cloud. Building defense

## Responses 1

Markdown supported · ⌘↵ to post

[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.