My goal is to only document issues that would break people's existing applications. So if you have a running app on AWS that makes use of some AWS API calls, what are changes AWS is making that require you to change your code, reconfigure, rebuild, or redeploy your application? Can it live forever as long as your credit card works, or is AWS potentially breaking something?
Any change has the potential to break something somewhere, but these seem like the more impactful changes for those that use the impacted service. These items will stay in this list until about a month after they have gone into effect, at which point they'll be removed.
|Date taking effect||Date announced||Service||Change||How to check|
|May 30, 2019||Unknown||Lambda||Support ends for runtime .NET Core 2.0; no longer able to update (link)||
|June 1, 2019||March 25, 2019||Mechanical Turk||Older versions of the MTurk Requester API (2014-08-15) will stop working (link)|
|June 11, 2019||May 14, 2019||Lambda||Execution environment update to Amazon Linux 2018.03 (link)||See link|
|June 30, 2019||Unknown||Lambda||Support ends for Node.js 6.10; no longer able to update (link)||
|July 22, 2019||May 21, 2019||EKS||Kubernetes 1.10 force updated to 1.11 (docs and blog)|
|July 31, 2019||Unknown||Lambda||Support ends for runtimes .NET Core 1.0 and 1.1; no longer able to update (link)||
|October 16, 2019||Unknown||Elastic Beanstalk||Windows Server 2008 R2 retired (link)|
|March 1, 2020||Unknown||Elastic Beanstalk||Apache HTTP Server 2.2, Nginx 1.12.2, GlassFish 4.x, Go 1.3–1.10, Java 6, Node.js 4.x–8.x, PHP 5.4–5.6, PHP 7.0–7.1, Python 2.6, 2.7, 3.4, Ruby 1.9.3, Ruby 2.0–2.3, Tomcat 6, Tomcat 8 (link)|
|April 1, 2020||Unknown||CloudHSM||Gemalto Luna 5 HSM's will be terminated (link)|
|April 30, 2020||April 21, 2019||CloudFront||API calls using code prior to 2016 will not work (link, screenshot)||link|
|June 24, 2020||July 11, 2018||S3||Signature must be v4 (link, screenshot). Any new buckets created after June 24, 2020 will not support SigV2 signed requests, although existing buckets will continue to support SigV2 while we work with customers to move off this older request signing method.||Enable CloudTrail S3 Data Events and check
|September 30, 2020||April 30, 2019||S3||Buckets created after September 30, 2020 must be accessed in the form <bucketname>.s3.amazonaws.com, not s3.amazonaws.com/<bucketname>/ (link)||See link|