AWS redshift documentation change
Summary
Revised Python UDF end-of-life details to include enforcement phases and blog publication date
Security assessment
The change only updates deprecation timelines and migration references. No security vulnerabilities, exploits, or security features are mentioned in the diff.
Diff
diff --git a/redshift/latest/mgmt/redshift-iam-access-control-idp-analytics-connecting-steps.md b/redshift/latest/mgmt/redshift-iam-access-control-idp-analytics-connecting-steps.md index 112d344f3..685b03dfc 100644 --- a//redshift/latest/mgmt/redshift-iam-access-control-idp-analytics-connecting-steps.md +++ b//redshift/latest/mgmt/redshift-iam-access-control-idp-analytics-connecting-steps.md @@ -9 +9 @@ Using an AWS IAM Identity Center and Redshift connection to query a data lakeUsi -Amazon Redshift will no longer support the creation of new Python UDFs starting Patch 198. Existing Python UDFs will continue to function until June 30, 2026. For more information, see the [ blog post ](https://aws.amazon.com/blogs/big-data/amazon-redshift-python-user-defined-functions-will-reach-end-of-support-after-june-30-2026/). +Amazon Redshift will no longer support the use of Python UDFs after June 30, 2026. We will start enforcing it in phases. For more information on the details of Python end of life and migration options, see the [ blog post ](https://aws.amazon.com/blogs/big-data/amazon-redshift-python-user-defined-functions-will-reach-end-of-support-after-june-30-2026/) that was published on June 30, 2025.