Boto3

Default retry behavior changing in 2026 — opt in now via AWS_NEW_RETRIES_2026=true. AWS announced a switch of boto3's default retry mode from legacy to standard (botocore 1.43.3+), reducing transient-failure noise for S3-heavy workloads. Available behind the env flag before it becomes the default — worth setting proactively in data pipelines. Per boto/boto3 discussion #4789.

Release cadence steady — latest PyPI release July 13, 2026. Per boto3 on PyPI.

GitHub. Boto3 is the Amazon Web Services (AWS) Software Development Kit (SDK) for Python. Notices: On 2026-04-29, support for Python 3.9 ended for Boto3. AWS is also developing the next major version of the AWS SDK for Python (experimental, async, bi-directional streaming). Per GitHub (boto/boto3).

GitHub. Benchmark comparing DuckDB, BigQuery, and Athena on 50GB Parquet. Uses boto3 for Athena benchmark setup. Results: DuckDB 5-8x faster, Athena 4.4x cheaper. Per GitHub (Insydia-Studio/benchmark-duckdb-athena-bigquery) (2026-01-26).

Urgent response needed: Boto3 and Botocore end of support April 2026. Boto3 and Botocore ended support for Python 3.9 on 2026-04-29. Users running older Python versions need to plan migrations to supported runtimes. Per GitHub (aws/sagemaker-scikit-learn-container) (2026-01-16).

Provide early development feedback on the next major version of the AWS SDK for Python. AWS released an experimental, non-GA next major version of the AWS SDK for Python. It uses modern Python paradigms, is asynchronous, supports bi-directional streaming, and currently only supports Bedrock Runtime. Install via uv pip install aws-sdk-bedrock-runtime. Per GitHub (boto/boto3) (2025-10-07).

Benchmarking Storage Performance (Latency, Throughput) Using Python. Python guide to benchmark AWS S3 storage performance using boto3. Measures upload/download/list latency and throughput to compare storage classes and optimize costs. Per dev.to (arjun_mullick_e734b4da656) (2025-07-14).

S3-compatible storage providers can break on boto3's newer PutObject defaults. Amazon extended the PutObject interface default starting with boto3 1.36.0, which some third-party S3-compatible services (e.g., IONOS Object Storage) don't yet support — workaround is pinning boto3<=1.35.99 or setting AWS_REQUEST_CHECKSUM_CALCULATION=when_required. Per IONOS Boto3 Python SDK docs.

Bedrock bearer-token auth doesn't propagate through boto3's SigV4 fallback path. boto3's native Converse API supports AWS_BEARER_TOKEN_BEDROCK, but auxiliary code paths that fall back through boto3's SigV4 credential chain don't recognize the bearer token, producing HTTP 403s — reported against an Anthropic SDK 0.87.0 integration. Per Hermes agent GitHub issue #29309. Sources: boto/boto3 discussion #4789 — updated default retry behavior · boto3 on PyPI · GitHub (boto/boto3) · GitHub (Insydia-Studio/benchmark-duckdb-athena-bigquery) · GitHub (aws/sagemaker-scikit-learn-container) · GitHub (boto/boto3) · dev.to (arjun_mullick_e734b4da656)