# 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.

- Workflow type: agent
- Services: AWS Lambda, Slack Bot
- Categories: Engineering, Operations
- Published: 2026-07-17

## What it does

- 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 you'll need

- 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

## Prompt

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.

## How to customize

- 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

## FAQ

### Does this actually change any of my Lambda functions?

No. The workflow only reads the function list and configuration. It never updates code, environment variables, or runtime settings.

### How does it know which runtimes are being deprecated?

The agent uses its own knowledge of the AWS Lambda runtime lifecycle instead of scraping AWS docs. Because it runs every weekday, it picks up newly announced deprecations without you touching the workflow.

### What happens on days when nothing is at risk?

You still get one short message so you know the scan ran and everything is currently fine.

### Will it work across multiple AWS regions?

Out of the box it scans the region tied to your AWS credential. To cover several regions, connect one credential per region and duplicate the workflow.

### Can I send the alert somewhere other than Slack?

Yes. Point the workflow at a different Slack channel, or ask the author to swap Slack for email, Teams, or a webhook to your on-call tool.

Use this prompt in General Input: https://www.generalinput.com/prompts/daily-slack-alerts-for-lambda-runtimes-nearing-end-of-support