This is very disappointing. I'm kind of amazed that they think this is a good business decision when there are massive numbers of paying customers with mountains of python code using boto3. I imagine much of that code uses the resource interfaces since they're easier to use.<p>This isn't some fringe feature they're deprecating; the official documentation uses these interfaces in its examples; they're literally telling you that's the correct way to use the library and then the next moment they're telling you it's not.
The AWS Python SDK team is no longer planning to support the resources interface in boto3. Requests for new changes involving resource models will no longer be considered, and the resources interface won't be supported in the next major version of the AWS SDK for Python. The AWS SDK teams are striving to achieve more consistent functionality among SDKs, and implementing customized abstractions in individual SDKs is not a sustainable solution going forward. Future feature requests will need to be considered at the cross-SDK level.
Is this to force customers to use CDK?<p><a href="https://aws.amazon.com/cdk/" rel="nofollow">https://aws.amazon.com/cdk/</a>
By "the next major version of the AWS SDK for Python" they must mean boto3 2.0.0, but I don't see any timeline or roadmap – the current version is 1.26.53 and it's been 1.x.x since July 2015. When will this actually be removed?