AWS CLI v1 enters maintenance mode with dependency changes
AWS CLI v1 will enter maintenance mode on July 15, 2026, changing how its botocore and s3transfer dependencies are managed. Instead of relying on standalone packages, these libraries will be vendored (bundled) directly into the CLI v1 codebase. This shift means upgrades to the standalone botocore and s3transfer packages will no longer affect CLI v1, and users with both CLI v1 and boto3 installed will have separate copies of these dependencies. AWS recommends migrating to AWS CLI v2 to ensure access to the latest AWS services and features.
- →AWS CLI v1 dependency management changes with maintenance mode
- →Impact on dependency updates and workflow compatibility
- →Recommendation to migrate to AWS CLI v2
- →Actions for users managing dependencies
Notes (4) ›
- AWS CLI v1 dependency management changes with maintenance mode
Starting July 15, 2026, AWS CLI v1 will enter maintenance mode, transitioning its botocore and s3transfer dependencies from standalone packages to being vendored directly within the CLI v1 codebase. This change means that upgrades to the standalone botocore and s3transfer packages will not impact CLI v1, and environments with both AWS CLI v1 and boto3 installed will contain duplicate copies of these libraries.
- Impact on dependency updates and workflow compatibility
Users upgrading AWS CLI v1 will no longer automatically receive updates for botocore and s3transfer through this process. The CLI v1 will use its internal, bundled versions, which will only be updated when AWS releases a new version of CLI v1 for critical fixes or security issues. This may affect workflows relying on automatic dependency updates and requires validation of existing scripts.
- Recommendation to migrate to AWS CLI v2
To ensure continued access to the latest AWS services, features, and improvements, AWS strongly recommends migrating to AWS CLI v2. A migration guide is available for assistance.
- Actions for users managing dependencies
Users should verify if their workflows depend on botocore or s3transfer through AWS CLI v1. If other applications in the same environment use these libraries, explicit pinning of dependency versions may be necessary. Monitoring the AWS CLI changelog is advised for updates on new versions and vendored dependency changes.
https://aws.amazon.com/blogs/developer/aws-cli-v1-maintenance-mode-announcing-changes-to-dependency-updates/
Related releases
- Terraform AWS Provider v6.60.0 Adds New Resources and Fixes Bugs Terraform AWS Provider Releases ·
- Amazon S3 enhances access denied errors with specific policy ARNs AWS What's New ·
- OpenAI Daybreak Red and Blue Cyber Defense Models Now on Amazon Bedrock AWS What's New ·
- AppFolio Transforms Data Streaming with Amazon MSK Express Brokers AWS Big Data Blog ·
- AWS IAM Role Manager Automates Service Role Setup AWS What's New ·
- Amazon Quick Integrates Microsoft Purview for Data Loss Prevention AWS What's New ·