AWS Glue 1.0 (Python 2) End of Life Date
AWS Glue 1.0 (Python 2) end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
AWS Glue 1.0-python-2 was released on July 25, 2019 and support ended on April 1, 2026 — a supported lifespan of 6 years and 8 months, in line with the 6 years and 8 months median for AWS Glue releases. It has been without security patches for 6 months. 1 newer AWS Glue release has shipped since.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| 0.9 | — | Apr 1, 2026 | EOL |
| → 1.0 (Python 2) | — | Apr 1, 2026 | EOL |
| 1.0 (Python 3) | — | Apr 1, 2026 | EOL |
| 2.0 | — | Apr 1, 2026 | EOL |
| 3.0 | — | EOL | Active |
| 4.0 | — | EOL | Active |
| 5.0 | — | EOL | Active |
| 5.1 | — | EOL | Active |
What does AWS Glue 1.0 (Python 2) end of life mean?
When AWS Glue 1.0 (Python 2) reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running AWS Glue 1.0 (Python 2) past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to AWS Glue 6.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.