- Newest
- Most votes
- Most comments
Based on the information available, I cannot confirm any official change to the .NET 6 runtime deprecation dates for AWS Lambda. The sources provided do not contain specific information about .NET 6 deprecation dates or any recent changes to them.
However, it's important to note that AWS does periodically update its runtime deprecation schedules. These dates are typically provided for planning purposes and can be subject to change. AWS usually communicates such changes through various channels, including email notifications, AWS Health Dashboard, and Trusted Advisor notifications.
For the most up-to-date and accurate information regarding runtime deprecation dates, it's always best to refer to the official AWS Lambda documentation. If you've noticed a discrepancy between different AWS sources, it would be advisable to contact AWS Support directly for clarification.
In general, AWS provides a significant notice period before deprecating runtimes. They typically send notifications 180 days before a runtime is deprecated. This allows customers time to plan and execute any necessary upgrades or migrations.
Regardless of the exact dates, it's recommended to start planning for the migration to a newer supported .NET runtime well in advance of the deprecation date. This ensures that your Lambda functions continue to receive security updates and remain eligible for technical support.
Sources
Managing AWS Lambda runtime upgrades | AWS Compute Blog
Lambda runtimes - AWS Lambda
Runtime maintenance in Lambda - Security Overview of AWS Lambda
Relevant content
- asked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated a year ago
