AWS Code Commit Ceased Onboarding New Customers • Hacker News Board

Re: AWS Code Commit Ceased Onboarding New Customers

#51

Post by belter » Tue, Jul 30, 2024, 11:35 AM UTC

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 running EC2 instances and managing the resilience and architecture.

This does not predict a good future for tools like Amazon CodeGuru Reviewer for Java and Python, CodeArtifact, CodePipeline and CodeBuild. And even if these plus QLDB were probably money losers for AWS, the MBA's are missing the point.

I would not be surprised if these silent decisions, are not reversed shortly, or if the service is just kept forever as is, but not deprecated.

Edit: Just found this

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

Don't know what is going on but now also Cloud9 seems to have a shaky future? Not on-boarding new customers?

AMZN Earnings Release is next Thursday after market close. https://www.nasdaq.com/market-activity/stocks/amzn/earnings

I am going to listen to that earnings call, very carefully....

Re: AWS Code Commit Ceased Onboarding New Customers

#52

Post by andrewstuart » Tue, Jul 30, 2024, 11:43 AM UTC

simonw wrote: post #15

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 releas…

Did anyone notice it is being cancelled?

Re: AWS Code Commit Ceased Onboarding New Customers

#53

Post by frikkie444 » Tue, Jul 30, 2024, 11:52 AM UTC

The worst thing about CodeCommit is that repo URLs are not unique, Depending on the AWS account you log in to, you can have a different repo with the same url.

Second worst thing is that it basically refuses to show a diff for any file longer than a few lines.

Third worst thing is you need a login helper and special generated credential to create a login.

Fourth worst thing is the absolute slowness of it. Good riddance.

Re: AWS Code Commit Ceased Onboarding New Customers

#54

Post by wordofx » Tue, Jul 30, 2024, 11:56 AM UTC

ffsm8 wrote: post #49

wordofx wrote: post #38

Earlier quoted context omitted.

> QLDB is an immutable database with allowing you to move back and forward in history and do live streaming of events etc with cryptographic verification built in. Which no one ever needed.

Eh, most people would like their apps to provide them with a browsable history of their data, and why the changes happened. It's just increases scope x100 to get anything done, so few do it... but if the tooling was available, almost all stateful applications would benefit from it.

lol no. And the DB isn’t going to tell you who what why without you writing code to support that audit in which case… that special database has solved exactly 0 problems that a traditional RDBMS already solves.

Re: AWS Code Commit Ceased Onboarding New Customers

#55

Post by zaphirplane » Tue, Jul 30, 2024, 12:11 PM UTC

ahoka wrote: post #42

wordofx wrote: post #38

Earlier quoted context omitted.

> QLDB is an immutable database with allowing you to move back and forward in history and do live streaming of events etc with cryptographic verification built in. Which no one ever needed.

Well, git is kinda popular.

What about Git rebase -i

Re: AWS Code Commit Ceased Onboarding New Customers

#56

Post by whazor » Tue, Jul 30, 2024, 1:01 PM UTC

upon_drumhead wrote: post #3

I once had high hopes Amazon would be able to build a real GitHub competitor. It's a real shame Amazon doesn't seem to be able to build anything that reaches beyond their walled garden.

They did: https://codecatalyst.aws/

Re: AWS Code Commit Ceased Onboarding New Customers

#57

Post by thr0w » Tue, Jul 30, 2024, 1:08 PM UTC

viccis wrote: post #16

Not surprised. CodeCommit was released alongside a stable of other mediocre tools for CI/CD (CodePipeline and CodeDeploy if I recall correctly) that reflected the pinnacle of AWS's mid-to-late 2010s attitude, which is to find something popular and offer an incredibly mediocre alternative to it that will still be used by those teams who want to move as much as possible to AWS. Seems like that stalled out a bit, mostly…

CodeDeploy is kinda good for blue/green deployments to EC2. A little painful to set up, but works flawlessly once you get it going.

Re: AWS Code Commit Ceased Onboarding New Customers

#58

Post by scarface_74 » Tue, Jul 30, 2024, 1:14 PM UTC

vasco wrote: post #19

viccis wrote: post #16

Not surprised. CodeCommit was released alongside a stable of other mediocre tools for CI/CD (CodePipeline and CodeDeploy if I recall correctly) that reflected the pinnacle of AWS's mid-to-late 2010s attitude, which is to find something popular and offer an incredibly mediocre alternative to it that will still be used by those teams who want to move as much as possible to AWS. Seems like that stalled out a bit, mostly…

Doesn't it reflect more on the quality of the people involved? These tools came out at the same time as a bunch of other AWS tools that are still used. The platform itself, the company around these teams was the same, so why did Code Commit suck but other AWS products from the same vintage turned out great?

You’ve never been part of a large organization have you?

I have a little insight on how things like CodeCommit fall behind the competition.

I worked at AWS in the Professional Services division. For a little over two years I was on a makeshift team maintaining and improving a very popular open source project in its niche.

The project was hosted on “AWS Samples” (https://github.com/aws-samples). Once approved for the initial release of a project in this Github organization, there is no oversite on updates. In my experience from releasing 8 of my own projects to the repository, it takes about two days to get the initial approval and it’s really based on the honor system as far as following the guidelines after that.

We released features and improvements like gangbusters based on customer demand or if we just wanted to scratch an itch.

Then, it became popular enough to be promoted from “AWS Samples” to an “AWS Solution” (https://aws.amazon.com/solutions/).

Everything slowed to a crawl, releases, approval processes, you had to justify everything you wanted to add based on revenue potential, everything had to be approved by higher ups. We were the sane developers. I dropped out of the project then.

But I saw the storm coming, so my last major contribution before it got transitioned was to introduce “hooks” functionality that allowed you to change the processing pipeline by adding a custom lambda arn to it in settings.

Before it became a “solution” former AWS employees who use to work on the project who were still in the industry would make changes and submit pull requests that we would merge.

But back to CodeCommit, can you imagine how hard it is to convince senior leadership to give you funding for a service that neither gives you a competitive advantage nor is a revenue generator?

Hell they just added support for viewing images inline in markdown from the console this year.

Re: AWS Code Commit Ceased Onboarding New Customers

#59

Post by jeffwask » Tue, Jul 30, 2024, 1:22 PM UTC

upon_drumhead wrote: post #3

I once had high hopes Amazon would be able to build a real GitHub competitor. It's a real shame Amazon doesn't seem to be able to build anything that reaches beyond their walled garden.

I've tried all of these tools over the last few years as part of vendor due diligence and none of them impressed me. Code Deploy is probably the best of the bunch and it's really just a very opinionated deployment tool that only works on specific use cases well.

Re: AWS Code Commit Ceased Onboarding New Customers

#60

Post by benterix » Tue, Jul 30, 2024, 1:27 PM UTC

grobbyy wrote: post #35

rgblambda wrote: post #23

Earlier quoted context omitted.

>be used by those teams who want to move as much as possible to AWS By teams that have been mandated to move as much as possible to AWS by their company's senior leadership, because it simplified accounts/they negotiated a "great contract" etc.

Having been on both sides, it often makes a lot of sense. A lot of companies have surprises requirements in contacts, such as HIPPA or military/classified or whatnot. The cost of adding a new vendor can be astronomical compared to the cost of dealing with CodeCommit. In truth, though, Amazon should have bought gitlab instead.

> In truth, though, Amazon should have bought gitlab instead.

We would be in very deep shit now.