4 ms·
AWS deprecates two dozen services (most of which you've never heard of)
- wdb 1y agoAh good old IoT Greengrass and Lambda that made me fail a job interview as it was my only AWS experience and the interviewers didn't belief it existed.
- jjtheblunt 1y agolanguage rant: titles with assertions that "you" have or have not $whatever...they seem lazily worded.
- devin 1y agoWhy do you think they’re “lazy”? The point is usually to bait you: “You’ll never guess this one weird trick!” Here it actually makes some sense. There are _so_ many AWS services. It’s similar to the quiz about AWS service icons that demonstrated that not only are the icons broadly unknown, there are myriad unknown services which further complicates things.
- jjtheblunt 1y agobait is definitely a better description, though i still think bait could be more effectively worded.
- CobrastanJorji 1y agoMan, deprecating an IoT APIs isn't going to affect most folks, but the folks it does affect are gonna be in a fuckload of trouble.
- cowsandmilk 1y agoIt says existing customers can continue to use the IoT apis, just not new customers.
- Aurornis 1y agoAWS has been good at leaving deprecated services running for existing customers for a long time. They’re doing that here. They’re deprecating it for new use cases.
- topher200 1y agoThis article is from mid-October.
- HumanOstrich 1y agoThanks, but the date is at the top of the article.
- NewJazz 1y agoWasn't there a big post about this a few weeks ago?
- learned 1y agoCodeCatalyst is pretty surprising on that list. Maybe it tried to do too much? Also, the deprecation alert on the CodeCatalyst site is incorrect at the moment: > Important Notice: Amazon CodeCatalyst is longer open to new customers starting on November 7, 2025 https://codecatalyst.aws/explore https://codecatalyst.aws/explore
- raw_anon_1111 1y agoIn my experience, any time AWS tries to create a service outside of the primitives, it’s a mess.
- tyre 1y agoI'm guessing it's just harder to dogfood in a way that others can use without all of the other internal-only infra (including dev tooling) available internally. And to get to the point where you could dogfood at AWS scale, anything that's difficult to adopt incrementally is going to be a pain.
- raw_anon_1111 1y agoExactly, no one internally is going to use something like Amplify or Code Catalyst. That’s like internal developers didn’t use CodeCommit (AWS’s now deprecated Git service). Even though it did hurt me when they got rid of CodeCommit. I work in consulting and I always ask for my own isolated dev AWS account in their organization with basically admin access. It was nice to just be able to put everything in CodeCommit without dealing with trying to be a part of their GitHub organization if their was red tape. I miss Cloud 9 too. I didn’t have to bother with making sure their computers were setup with all of the pre requisites and it gave me a known environment for the handover
- donavanm 1y agoThey tried to do a LOT. An absolutely huge amount of work trying to abstract all of the existing Code* services, big chunks of other AWS services, and then corp (and non corp!) identity. The last part, getting human identity in to AWS, is such a fundamental gap. In the end its unsurprising that they couldnt get to a competitive place against gitlab/github/etc. I do hope theres more success with identity center picking up some of those IdP pieces.
- hinkley 1y agoDoes the service list fit on a 4k monitor with these removed?
- sunrunner 1y agoHorizontal or vertical orientation?
- hinkley 1y agoIt’s been a while since I was dumb enough to try to use the menu system. What a useless sea of unhelpful product names and icons. Doesn’t it adjust? But in any case, does it fit in any orientation at all?
- dotancohen 1y agoYou have to know these things when you're a king.
- IgorPartola 1y agoAWS has so many services at this point and it feels like so many of them overlap too. Seems like for a while they basically just took any open source project that was somewhat popular and offered a managed version of it. Plus there is a marketplace where others can offer services. The landscape is so vast it feels overwhelming to even try to get a basic layout. For personal projects I end up avoiding AWS and instead prefer things like the Backblaze S3-compatible object storage, Vultr for VMs, and so on just to avoid the power user features that will only get in the way. With that, I am curious how people who do not have an enterprise-size team to manage their AWS infrastructure navigate their offerings.
- pram 1y agoFrom my observations over the years a lot of “services” should literally just be features in stuff that already exists. Like Flink should have just been under MSK instead of the confusing mess it has gone through (first branded as part of Kinesis???)
- sethhochberg 1y agoI always find the idea that there's something to navigate kind of curious - as you say, its lots of managed versions of open source tools and a mix of proprietary management frameworks on top. Some of what they offer are genuinely unique products for niche use cases, but if you have that niche you probably know what services can support it, like the people in the other comments here mentioning the IoT APIs. But me (or my teams) are rarely asking the question of "how should I run my service on AWS" in general, its much more typically "I need a managed Postgres database, what AWS product offers that" or "I have an OCI image, what managed platform can I run that in" or even "I want this endpoint to be available all the time, but its usage is very unpredictable/intermittent, so I don't want to pay for idle compute". There might still be a couple of possible answers for those questions, but by the point I arrive there I'm solving for a specific problem. Its sort of like walking into a kitchen hungry and seeing 3 knives and a stove and oven and a dozen peelers and can openers etc etc and being very overwhelmed by all of this (do I need the knife with a smooth edge or the serrated one?) until you decide you want to eat a grilled cheese, and then grabbing a skillet to put onto a burner and everything making sense once you actually start to cook a specific thing.
- gnabgib 1y agoDiscussion (69 points, 1 month ago, 35 comments) https://news.ycombinator.com/item?id=45572613 https://news.ycombinator.com/item?id=45572613
- cperciva 1y agoAWS has done its quarterly housecleaning / “Googling” of its services Note: This is actually two quarters of Googling, because they were revising their process during Q3 and put deprecations on hold.
- more_corn 1y agoElastic beanstalk or GTFO
- odie5533 1y agoI think they accidentally convinced too many people to use it and now they can't get rid of it.
- deleted 1y ago[deleted]
- rs186 1y agoAnyone can predict what's going to happen with Amazon Q? The only people that I know or have seen using Amazon Q are internal employees. Almost nothing on reddit.
- easton 1y agoIt’s definitely fine for a while, it’s the closest thing they have to an internal chatbot product and they need that to sell enterprises on adopting AWS.
- righthand 1y agoAnecdotally, I tried using Amazon Q when trying to generate configs and get questions answered for Aws ses configs. However even though: the icon was on my screen and fully functioning and I could enter a question, I could not send the question or use it because my admin had not granted my dev profile access to use Amazon Q. And my guess is that people have that same experience and give up. Because the admin permissions are probably stored in a yaml config somewhere and it will require a meeting with a devops admin and ultimately be a huge waste of time for answering 1-2 questions.
- dherls 1y agoI like how the article uses "Googling" as a verb meaning to shut down a service
- oytis 1y agoThank you, I failed to understand what he means.
- yreg 1y agoReminds me of the '168 AWS Services in 2 minutes' song https://youtu.be/BtJAsvJOlhM https://youtu.be/BtJAsvJOlhM
- vivzkestrel 1y agoAWS really needs to focus on simplifying their offerings for the next generation that is not very "computer savvy" for starters. You can host a website on ec2, you can also host it on elastic beanstalk, you can also host it on lightsail? See the problem? Instead of making us focus on how to adapt to your services, why not focus on how you can adapt to the customer needs. Introduce something called AWS WebServer or something and deprecate everything else except EC2. let people run their docker and lightsail and static hosting from this Amazon WebServer service. Do the same for databases. Why offer a separate Amazon Aurora postgres and an amazon RDS. Offer a service called Amazong DB and let the user decide if it is posgres, server oriented, serverless from there. Let it also handle dynamoDB
- nasmorn 1y agoAWS makes money being the Hoster of Fortune 500 companies. They want lots of complicated shit. AWS has no problem that hobbyists or small business choose simpler solutions elsewhere
- dotancohen 1y agoMany of those simpler solutions, such as Vercel, are themselves hosted on AWS.