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 from endoflife.date and official vendor documentation.
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 4 months.
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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running AWS Glue 1.0 (Python 2) past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to AWS Glue 5.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.