NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #3759 most downloaded on PyPI
AWS IoT SDK based on the AWS Common Runtime
Last release 2 months ago
24 Jul 2026
Ships fairly regularly
a new release about every 2 months
Nearly every release is documented
notes for 59 of the last 60 stable releases
3 versions withdrawn
withdrawn after publishing
7 years old
93 releases · first in 2019
New APIs added to the Greengrass IPC client
On Windows, always perform an SNI check even with an overridden root CA
One column per quarter.
Http proxies can now be used with direct mqtt connections, not just websockets
Python3.5 is EOL, remove support for it.
__version__ to the packageUse awscrt 0.11.17, which is working again on piwheels.org for python 3.7
More validation of HTTP/1.1 messages (#273); from aws-crt-python->aws-c-http
BUGFIX: several memory leaks fixed
awsiot.eventstreamrpc (used by greengrasscoreipc) had circular references the gc could not clean upawscrt.eventstream.rpc.ClientConnection was leaking its native partawscrt.eventstream.rpc.ClientContinuation was leaking incoming headersawscrt.http.HttpRequest was leaking its headersawscrt.auth.AwsSigningConfig was leaking its native partawscrt.auth.aws_sign_request() was leaking native native dataThis is a re-release of what should have been v1.5.11 which did not have the right tag name.
This is a re-release of what should have been v1.5.11 which did not have the right tag name.
Nothing published for this version
Updated MQTT to configure protocol operation timeout
Nothing published for this version
Updating dependency to pick up event stream RPC client fix.
Nothing published for this version
MQTT on-message callbacks have new qos, retain, and dup args. This is a backwards-compatible change.
MQTT on-message callbacks have new qos, retain, and dup args. This is a backwards-compatible change.
Allow custom credentials providers via awscrt.auth.AwsCredentialsProvider.new_delegate()
Nothing published for this version
Added EventStream RPC capability
BUGFIX: update to awscrt 0.9.10, the previous version was missing wheels for python 3.8 and 3.9 on Linux x86_64, and missing all Linux aarch64 wheels.
Updated to v0.9.3 of Python CRT
Updated to v0.9.3 of Python CRT (#117)
MAJOR CHANGE: Remove support for Python 2, Python 2.7 was end of life Jan 1, 2020.
API CHANGE: awscrt.auth.AwsSigningConfig.signed_body_value is now a string instead of an enum.
Nothing published for this version
fixes a variety of bugs, including
In these notes we detail exactly what happened, who is affected by the breaking change, and how we are addressing it both right now and looking toward…
With the 1.2.0 release of the V2 Iot Device SDK for Python, a serious backwards incompatibility was introduced due to an oversight in the code generation for the constructors of service model classes. This release corrects this incompatibility and reworks service model construction with a pattern that will prevent it from happening again. In these notes we detail exactly what happened, who is affected by the breaking change, and how we are addressing it both right now and looking towards the future.
The 1.2.0 (named shadow) release saw the introduction of new APIs to support named shadows, but it also introduced a new parameter, client_token, to the GetShadow and DeleteShadow APIs. The code generator for the constructor for the request and response classes took the list of parameters and sorted them before generating the code. Since client_token comes before thing_name lexically, this resulted in client_token becoming the first parameter to the class constructor. Any programs calling GetShadow or DeleteShadow using thing_name as the first positional parameter were broken by this change (assuming an upgrade to 1.2.0). This includes the shadow sample itself.
Who was affected by this breaking change? Anyone who upgraded to a 1.2.x version of the SDK who had a program that used either the GetShadow or DeleteShadow APIs.
To fix this, we settled on the following solution:
The upgrade to 1.3.x and beyond will not break any working programs built against any version of the SDK and will restore programs that were broken by 1.2.x to a working state.
Going forward, all new parameters to service model class construction will be keyword only. All samples have been updated to reflect this new pattern.
We apologize for this customer-breaking mistake and, in addition to fixing it, we are in the process of improving our CI infrastructure to help prevent breaking changes from reaching our customers again.
Update awscrt dependency to 0.6.0, which brings in API changes to awscrt.auth
Update awscrt dependency to 0.6.0, which brings in API changes to awscrt.auth
Nothing published for this version
Fleet provisioning Co-authored-by: Justin Boswell boswej@amazon.com
Fleetprovisioning (#58)
Fleet provisioning Co-authored-by: Justin Boswell boswej@amazon.com
Upgrade awscrt to version 0.5.13
Upgrade awscrt to version 0.5.13
Bugfix:
HTTP API Change:
awscrt.HttpClientStream must have .activate() called before it will begin sending/receiving data.Update awscrt to version 0.5.11. Improvements include:
Update awscrt to version 0.5.11. Improvements include:
on_connection_resumed callback's return_code argument.Note that awsiotsdk 1.0.4 never publicly released.
Update awscrt dependency, now has wheels for aarch64 and Python3.8
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →