Need advice about which tool to choose?Ask the StackShare community!
AWS CodeCommit vs GitHub Enterprise: What are the differences?
Developers describe AWS CodeCommit as "Fully-managed source control service that makes it easy for companies to host secure and highly scalable private Git repositories". CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools. On the other hand, GitHub Enterprise is detailed as "The on-premises version of GitHub, which you can deploy and manage in your own, secure environment". GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services.
AWS CodeCommit and GitHub Enterprise can be categorized as "Code Collaboration & Version Control" tools.
Some of the features offered by AWS CodeCommit are:
- Collaboration
- Encryption
- Access Control
On the other hand, GitHub Enterprise provides the following key features:
- Compliance and auditing
- Hundreds of integrations
- Flexible deployment
DuckDuckGo, OkCupid, and Shutterstock are some of the popular companies that use GitHub Enterprise, whereas AWS CodeCommit is used by iMedicare, Complete Business Online, and Sidecar Interactive. GitHub Enterprise has a broader approval, being mentioned in 38 company stacks & 46 developers stacks; compared to AWS CodeCommit, which is listed in 24 company stacks and 17 developer stacks.
We are using a Bitbucket server, and due to migration efforts and new Atlassian community license changes, we need to move to a new self-hosted solution. The new data-center license for Atlassian, available in February, will be community provisioned (free). Along with that community license, other technologies will be coming with it (Crucible, Confluence, and Jira). Is there value in a paid-for license to get the GitHub Enterprise? Are the tools that come with it worth the cost?
I know it is about $20 per 10 seats, and we have about 300 users. Have other convertees to Microsoft's tools found it easy to do a migration? Is the toolset that much more beneficial to the free suite that one can get from Atlassian?
So far, free seems to be the winner, and the familiarization with Atlassian implementation and maintenance is understood. Going to GitHub, are there any distinct challenges to be found or any perks to be attained?
These are pretty competitive, and to recommend one over the other would require understanding your usage. Also, what other tools you use: for instance, what do you use for Issue-tracking, or for build pipelines. In your case, since you are already using Bitbucket, the question would be: do you have any current pain-points? And, on the other hand, do you already use Atlassian's JIRA, where you'd benefit from the tight integration? So, though I would not recommend one over the other just in general,. But, if Bitbucket fulfills your current use-cases, then there seems to be little motivation to move.
Hi, I need advice. In my project, we are using Bitbucket hosted on-prem, Jenkins, and Jira. Also, we have restrictions not to use any plugins for code review, code quality, code security, etc., with bitbucket. Now we want to migrate to AWS CodeCommit, which would mean that we can use, let's say, Amazon CodeGuru for code reviews and move to AWS CodeBuild and AWS CodePipeline for build automation in the future rather than using Jenkins.
Now I want advice on below.
- Is it a good idea to migrate from Bitbucket to AWS Codecommit?
- If we want to integrate Jira with AWS Codecommit, then how can we do this? If a developer makes any changes in Jira, then a build should be triggered automatically in AWS and create a Jira ticket if the build fails. So, how can we achieve this?
Hi Kavita. It would be useful to explain in a bit more detail the integration to Jira you would like to achieve. Some of the Jira plugins will work with any git repository, regardless if its github/bitbucket/gitlab.
Pros of AWS CodeCommit
- Free private repos43
- IAM integration26
- Pay-As-You-Go Pricing23
- Amazon feels the most Secure19
- Repo data encrypted at rest18
- I can make repository by myself if I have AWS account11
- Faster deployments when using other AWS services11
- AWS CodePipeline integration7
- Codebuild integration6
- Does not support web hooks yet! :(6
- Cost Effective4
- No Git LFS! Dealbreaker for me2
- Elastic Beanstalk Integration2
- Integrated with AWS Ecosystem2
- Only US Region1
- Issue tracker1
- Open source friendly1
- Available in Ireland (Dublin) region1
- CodeDeploy Integration1
- CodeCommit Trigger for an AWS Lambda Function1
- Integration via SQS/SNS for events (replaces webhooks)1
- IAM1
- Ui0
Pros of GitHub Enterprise
- Code security2
- CDCI with Github Actions2
- Expensive - $$$2
- Both Cloud and Enterprise Server Versions available1
- Draft Pull Request1
Sign up to add or upvote prosMake informed product decisions
Cons of AWS CodeCommit
- UI sucks11
- SLOW4
- No Issue Tracker3
- Bad diffing/no blame2
- No fork2
- No webhooks2
- NO LFS support2
- Can't download file from UI1
- Only time based triggers1
- Accident-prone UI0
Cons of GitHub Enterprise
- $$$1
