The tweet took Lyft's total AWS costs and divided it by total rides. It's not a literal accounting of the compute cost for a single ride. AWS costs that wouldn

The tweet took Lyft's total AWS costs and divided it by total rides. It's not a literal accounting of the compute cost for a single ride. AWS costs that wouldn't really fit into a per-ride accounting: * Redundancy of instances (regions/AZs) * Data-storage/duplication/backups * Non-ride related AWS costs (hosting/processing of analytics, test & automation infrastructure, etc.) I'm sure there are others. I'm not saying that there's no way they could get their AWS costs down, btw.