Daily Slack alerts for Lambda runtimes nearing end of support

Every weekday at 9am, scan every AWS Lambda function in the account for runtimes that AWS has deprecated or is about to retire, and post a single Slack summary.

Use the AWS Lambda List Functions operation to enumerate every function in the account and region. For each function returned, call the AWS Lambda Get Function Configuration operation and read the Runtime field (values like nodejs20.x, python3.11, java17, dotnet8, ruby3.3, provided.al2023, and so on), the FunctionName, and the LastModified timestamp.

Apply your own knowledge of the AWS Lambda runtime deprecation calendar rather than scraping AWS docs. Flag any function whose runtime AWS has already ended support for, or whose runtime reaches end of support within the next 60 days. For each flagged function, capture the function name, the runtime identifier, the last-modified date, and the deprecation deadline.

Post a single message with the Slack Bot Send a Message operation to the platform channel. Group the flagged functions by runtime, and under each runtime heading list function name, last-modified date, and deadline. If nothing is at risk, post one short all-clear line for the day instead so it is obvious the scan ran.

This workflow is read-only: never call any operation that creates, updates, invokes, or deletes a Lambda function.