Do you use Python CustomResources in your CloudFormation stacks?
If so, you need to act before 01 April 2021.
You may have already received correspondence directly from AWS but here's your final reminder that if you use Python for CloudFormation Lambda backed CustomResources, then you may need to act before 01 April 2021.
Starting on 01 April 2021, AWS Lambda [will no longer support][1] the botocore.vendored.requests library in Python runtimes.
Any AWS CloudFormation stacks that use the Python runtime for Lambda-backed Custom Resources must be updated to ensure you can continue to maintain your cloud infrastructure. If you do not act now, after 01 April 2021 you will no longer be able to create, update or delete those custom resources.
For more information on the background to the change, please see the [referenced blog post][1]
Any CloudFormation stacks containing Python-based custom resources must be updated before 01 April 2021.
Using CloudFormation across your AWS estate means this is not a trivial issue.
We have developed a [command line tool][2] to help you identify any impacted resources across your estate.
We have worked examples in the [tool readme][2]
What you must do depends on how you have packaged your [custom resources][3]:
cfn-response implicitly using inline code using ZipFile: then you need to perform a change to trigger an update (see [this link][2] for an example)If you need assistance, [please get in touch][4]!
1 https://aws.amazon.com/blogs/compute/upcoming-changes-to-the-python-sdk-in-aws-lambda/ 2 https://github.com/MechanicalRock/aws-cfnresponse-checker 3 https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-lambda-function-code-cfnresponsemodule.html 4 https://www.mechanicalrock.io/lets-get-started