AWS redshift documentation change
Summary
Revised Python UDF end-of-life notice to clarify termination timeline and blog post details
Security assessment
Change documents feature deprecation schedule only. Absence of security-related terms like 'vulnerability', 'patch', or 'exploit' indicates non-security nature.
Diff
diff --git a/redshift/latest/dg/getting-started-federated-CF.md b/redshift/latest/dg/getting-started-federated-CF.md index 377f44534..3b63b52ce 100644 --- a//redshift/latest/dg/getting-started-federated-CF.md +++ b//redshift/latest/dg/getting-started-federated-CF.md @@ -9 +9 @@ Launching a CloudFormation stack for Redshift federated queriesQuerying data fro -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.