aws_breaking_changes

Most years, AWS increases some prices: https://github.com/SummitRoute/aws_breaking_changes/blob/mai...

Better start keeping an eye on this page: https://github.com/SummitRoute/aws_breaking_changes

SimpleDB, S3 Select, old style EC2s outside VPCs, QLDB, AWS Data Pipelines, Cloud9, CodeCommit, SnowMobile, Forecast are the ones I know. A few more can be found at: https://github.com/SummitRoute/aws_breaking_changes https://www.thestack.technology/aws-deprecations-services-co... From the outside I dont perceive the promotion dynamics for engineers working on old services is that different at AWS than Google or Azure. Finance and engineering do conspire to kill off things despite customer annoyance, perhaps as they should. There is also a constant churn of retiring EC2 instance types, security certs, old database versions, EMR versions, OS versions, security practices, cost optimizations, etc to suck up your time with minimal business value. This is not different fundamentally than on prem, you just have slightly less control and an out

"AWS breaking changes and price increases" - https://github.com/SummitRoute/aws_breaking_changes?tab=read...

This is very bad, and the silent deprecation of Amazon QLDB even more shocking. It looks like at AWS the MBA's are fully in charge... Many in this thread commenting on CodeCommit not being GitHub or GitLab are missing the point. I don't want to have my companies code with GitHub/Microsoft and being used to train their AI. Also don't want to have to rely on a third party like GitLab, that is a company who makes no money, and whose losses are $55 million dollars a quarter, and has shaky internal technical governance. Did not forget about their Prod database one man setup.... I don't care about the lack of features of CodeCommit. It's usefulness was essentially providing a managed git server. Did not need more, but needed it as a managed server in the AWS Cloud. The alternatives now will be the third parties, or the additional effort of runn

In writing this up - https://simonwillison.net/2024/Jul/30/aws-codecommit-quietly... - I found out about a much more significant deprecation: Amazon QLDB (Quantum Ledger Database - a blockchain-ish thing they launched in GA in 2019) is being hard-deprecated too! They're shutting it down completely on 31st July 2025, having announced the shutdown a few weeks ago (on July 18th). QLDB shutdown announcement in the release notes: https://docs.aws.amazon.com/qldb/latest/developerguide/docum... Their blog post about how to rewrite QLDB apps to use Aurora PostgreSQL instead: https://aws.amazon.com/blogs/database/migrate-an-amazon-qldb... Hacker News discussion from when QLDB was first announced in 2018: https://news.ycombinator.com/item?id=18553387 I also found this handy community GitHub repo which tracks these breaking AWS changes and lets you

https://awsapichanges.info/ will interest you, as might * https://github.com/z0ph/MAMIP#readme * https://github.com/SummitRoute/aws_breaking_changes#readme I thought there was a backing github repo for AwsApiChanges.info but I was unable to readily locate it