I have a mental model of AWS as almost never breaking anything (my S3 bucket has worked for 15+ years now), but I may need to update that model.
AWS quietly deprecated both AWS CodeCommit (Git hosting) and AWS QLDB (a blockchain database thing) in the past few weeks. Notes here: https://simonwillison.net/2024/Jul/30/aws-codecommit-quietly-deprecated/
The QLDB deprecation is particularly tough, because it leaves customers of that service needing to do effectively a complete rewrite to run against a less weird database. Amazon's recommendation is to rewrite things to use Aurora PostgreSQL, as described by this comprehensive and intimidating blog post https://aws.amazon.com/blogs/database/migrate-an-amazon-qldb-ledger-to-amazon-aurora-postgresql/
@simon some of these have in common that they're not really the low-level substrate that AWS is known for but some grafted-on buzzwordy me-too stuff (e.g., Cloud9, AppStream, Finspace Dataset Browser, QLDB, Workdocs, Mobile Hub) or some now rather dated tech stacks (OpsWorks). But I always viewed CodeCommit as potentially good for resilience since you don't want to have your AWS stack's CI depend on some other hotshot startup's high level Rube Goldberg machine that may go into maintenance mode at the slighest disturbance at Azure, GCP or AWS itself, for that matter, so that's a bit shocking to me (fortunately we never used that).
@christiankothe @simon using anything except GitHub is a calculated risk.