AWS CLI v1 enters maintenance mode
AWS announced AWS CLI v1 will enter maintenance mode on July 15, 2026, with full support ending July 15, 2027 — signaling teams must plan migration to v2 to avoid losing support. That gives engineering teams a predictable window to update automation scripts and CI/CD agents. (x.com)
AWS says v1 will receive only critical bug fixes and security patches during maintenance and that it will not receive new features, new service support, or region expansions. (aws.amazon.com) Two AWS-owned migration aids are recommended: Upgrade Debug Mode (built into AWS CLI v1) and the standalone AWS CLI v1-to-v2 Migration Tool (a Python package that can lint and modify bash scripts). (docs.aws.amazon.com) Upgrade Debug Mode requires AWS CLI v1 version 1.44.0 or later and can detect 14 of the 15 breaking changes listed in the CLI v2 breaking-changes guidance. (aws.amazon.com) The v1-to-v2 Migration Tool is specifically able to automatically update many AWS CLI v1 commands in shell scripts to preserve behavior when switching to v2. (docs.aws.amazon.com) AWS documents that AWS CLI v2 removes the separate Python dependency (the installer bundles what it needs) and includes features not backported to v1, making some workflows incompatible without changes. (docs.aws.amazon.com) When both versions are present the system uses the first aws found in PATH, so AWS recommends uninstalling v1 or using OS-level symlinks/aliases if both need to coexist during migration. (docs.aws.amazon.com) The v1 pip package metadata and repository notes already carry the maintenance notice and recent v1 patch releases (for example PyPI shows current v1 releases with a maintenance-mode message), indicating AWS will continue security patches through the maintenance window. (pypi.org)
