AWS Lambda dotnetcore3.1 end of life (EOL) date and support status
End of life End of life since 2023-05-03 (1254 days ago)
Upgrade: AWS Lambda dotnetcore3.1 no longer receives fixes. Supported cycles: java17.al2023, java11.al2023, java8.al2023, ruby4.0, dotnet10, nodejs24.x, python3.14, java25, ruby3.4, dotnet9, nodejs22.x, python3.13, ruby3.3, dotnet8, python3.12, java21, nodejs20.x, provided.al2023, python3.11, ruby3.2, java17, python3.10, nodejs18.x, nodejs16.x, dotnet6, python3.9, nodejs14.x, java8.al2, provided.al2, ruby2.7, python3.8, java11, provided, python3.7, go1.x, java8.
| Product | AWS Lambda |
|---|---|
| Version cycle | dotnetcore3.1 |
| Status | End of life |
| Released | 2020-03-31 |
| Active support until | 2023-04-03 |
| End of life | 2023-05-03 |
| Latest version | — |
| Last verified | 2026-10-08 |
All AWS Lambda versions → · Source: endoflife.date
Frequently asked questions
Is AWS Lambda dotnetcore3.1 end of life?
Yes. End of life since 2023-05-03 (1254 days ago). It no longer receives security or bug fixes.
When does AWS Lambda dotnetcore3.1 reach end of life?
AWS Lambda dotnetcore3.1 reached end of life on 2023-05-03.
When was AWS Lambda dotnetcore3.1 released?
AWS Lambda dotnetcore3.1 was first released on 2020-03-31.
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
For agents
GET https://vigia.coredls.cloud/v1/eol/aws-lambda/dotnetcore3.1