Daily Slack alerts for Lambda runtimes nearing end of support
Every weekday at 9am, get a Slack heads-up on the AWS Lambda functions running a runtime AWS is about to retire.
AWS Lambda
Slack BotEngineeringOperationsNotifications & AlertsResearch & MonitoringEvery 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.
What does this prompt do?
- Wakes up every weekday at 9am and looks at every AWS Lambda function in your account
- Checks the runtime each function is on against the AWS Lambda deprecation calendar
- Flags anything already deprecated or reaching end of support within the next 60 days, with the function name, runtime, last-modified date, and deadline
- Posts one tidy Slack message to your platform channel grouped by runtime, or a short all-clear line if nothing needs attention
What do I need to use this?
- An AWS account with a read-only IAM key that can list and describe Lambda functions
- A Slack workspace with the platform channel the bot should post into
How can I customize it?
- Change the schedule (every weekday, just Mondays, or hourly) and the 60-day warning window
- Swap the Slack channel or add on-call handles so the right people get pinged
- Narrow the scan to a single region, tag, or environment prefix
FAQs
Does this actually change any of my Lambda functions?
How does it know which runtimes are being deprecated?
What happens on days when nothing is at risk?
Will it work across multiple AWS regions?
Can I send the alert somewhere other than Slack?
Related templates
Every logo, photo, video cut and ad export in one searchable grid, with previews, campaign tags and rights expiry dates at a glance.
Twice a day we spot the people clicking your pricing and demo pages, create a follow-up task for their owner, and post a ranked recap to Slack.
One board showing every dashboard and Look with its folder, owner and favorite count, so you can find dead content and retire it safely.
Watch every live room on one screen, remove disruptive guests, start recordings and end stuck sessions without anyone opening a terminal.
Every Monday we find leads who never bought, research a real reason to reach out, and send a short personal email instead of another check in.
See the exact hours your chat queue backs up and customers give up waiting, then plan next week's shifts before it happens again.
Never get caught by a Lambda runtime retirement again.
Set this scan running once and let it flag at-risk functions in Slack every weekday morning.