# Locust vs AWS Distributed Load Testing

> Locust is an open source, self-hosted load testing tool from Locust authors, scripted in Python. AWS Distributed Load Testing is an open source, vendor-hosted cloud load testing service from Amazon Web Services, scripted in Java, JavaScript. The practical split is who runs the load generators: Locust on your own infrastructure, AWS Distributed Load Testing on the vendor's.

- Canonical: https://perf.jmeter.ai/vs/locust-vs-aws-distributed-load-testing/
- Compared: [Locust](https://perf.jmeter.ai/tools/locust/) · [AWS Distributed Load Testing](https://perf.jmeter.ai/tools/aws-distributed-load-testing/)

## Verdict
Both cover HTTP, HTTPS. On recorded coverage Locust is the wider of the two (3 protocols against 2), which matters only if your workload actually uses the extra ones. Data residency and who operates the generators usually settle Locust against AWS Distributed Load Testing. Run the same scenario on both before you standardize; the rows below only tell you what is true on paper.

## Specs
| Field | Locust | AWS Distributed Load Testing |
| --- | --- | --- |
| Vendor | Locust authors | Amazon Web Services |
| Category | Load Testing | Cloud Load Testing |
| License | Open Source | Open Source |
| Deployment | Self-hosted | Cloud |
| Status | Active | Active |
| First released | 2011 | 2018 |
| Pricing | Free; MIT License. | Free solution code; pay AWS infrastructure costs. |
| Scripting | Python | Java, JavaScript |
| Protocols | HTTP, HTTPS, WebSocket | HTTP, HTTPS |
| OS support | Windows, macOS, Linux | Linux |

## How to choose
- Pick AWS Distributed Load Testing to avoid operating injectors, Locust when residency or air-gapped runs rule a hosted service out.
- Only Locust records support for WebSocket — one hard requirement there decides the pair on its own.
- Match the authoring language to the team: Locust means Python, AWS Distributed Load Testing means Java, JavaScript.
- Open the Test Rig to compare license, deployment, protocol and OS rows side by side.

---
Curated by NaveenKumar Namachivayam (QAInsights) · methodology: https://perf.jmeter.ai/about/#methodology · corrections: https://github.com/QAInsights/Performance-Testing-Tools/issues/new?title=Tool%20submission%3A%20&body=Tool%20name%3A%20%0AOfficial%20URL%3A%20%0AWhat%20should%20be%20added%20or%20corrected%3F%20%0A