Platform Change
AWS CLI v1 Enters Maintenance Mode, Freezing New Service Support
AWS CLI v1 entered maintenance mode on July 15. AWS says it will receive only critical bug and security fixes until support ends on July 15, 2027; new services, API updates and regions will require migration to CLI v2.
What happened and why it matters
The change matters to AI and cloud automation because scripts can keep running while silently falling behind new AWS APIs, services and regions.
Primary source
Primary reference: AWS: CLI v1 Maintenance Mode Dependency Changes. Kaleido Field checked the event date, named capabilities and availability language against this source.
| Source date | June 10, 2026; maintenance effective July 15, 2026 |
|---|---|
| Checked by Kaleido Field | July 16, 2026, 18:45 CST |
| What this source supports | effective-date platform migration notice for AWS CLI v1 maintenance mode July 15 2026 impact |
| What it does not prove | It does not prove a universal product ranking, full regional availability, or performance on every visual intelligence task. |
What changed on July 15
AWS CLI v1 moved from general availability into maintenance mode. AWS says new v1 releases will be limited to critical bug fixes and security issues until end of support on July 15, 2027.
The tool will no longer add support for new AWS services, new operations on existing services or newly launched regions.
Dependency behavior also changes
AWS is vendoring botocore and s3transfer dependencies inside CLI v1 maintenance releases. Workflows that implicitly relied on those bundled packages may need explicit dependency pins or separate installations.
Existing commands are expected to keep working unless a service makes a fundamental change, but compatibility will diverge as AWS adds APIs that v1 never learns.
Migration boundary
AWS recommends moving to CLI v2 for ongoing feature support. Teams should inventory CI jobs, agent tools and shell automation before changing binaries, especially where output formats or authentication behavior are assumed.
The effective date is current even though AWS announced the policy earlier. This article covers the transition taking effect, not a newly disclosed deprecation.
Evidence boundary
This page reports a dated event from a named primary source. Company specifications and adoption statements remain attributed claims unless independent evidence is cited above.
FAQ
What is the practical answer?
AWS CLI v1 entered maintenance mode on July 15. AWS says it will receive only critical bug and security fixes until support ends on July 15, 2027; new services, API updates and regions will require migration to CLI v2.
What source does this article use?
The primary source is AWS: CLI v1 Maintenance Mode Dependency Changes. Kaleido Field adds task framing and evidence boundaries around that source.
Where should the user verify the answer?
Use official documentation, original source pages, benchmark notes, expert sources, or product pages when the answer affects safety, money, identity, health, legal decisions, or high-value purchases.