Need advice about which tool to choose?Ask the StackShare community!
AWS CodeCommit vs GitHub Enterprise: What are the differences?
AWS CodeCommit and GitHub Enterprise are popular version control platforms that offer similar functionalities but have key differences.
Code Hosting: AWS CodeCommit is a fully managed, secure, and scalable version control service, while GitHub Enterprise is an on-premises version control solution. CodeCommit is offered as a service in the AWS cloud, making it easily accessible and eliminating the need for infrastructure setup and maintenance. GitHub Enterprise, on the other hand, requires installation and configuration on local servers.
Integration with Other AWS Services: CodeCommit seamlessly integrates with other Amazon Web Services (AWS) services, such as AWS CodeBuild, AWS CodeDeploy, and AWS CodePipeline, providing a complete DevOps solution. It allows for automated deployments and continuous integration workflows within the AWS ecosystem. GitHub Enterprise does not have the same level of integration with AWS services.
Pricing Model: AWS CodeCommit follows the pay-as-you-go pricing model, where users are billed based on the storage, number of repositories, and data transfer. GitHub Enterprise, on the other hand, has a fixed pricing structure that requires a subscription for a specified number of users. This difference in pricing models allows for more flexibility with CodeCommit and can be cost-effective for smaller teams.
Access Control: CodeCommit offers fine-grained access control through AWS Identity and Access Management (IAM) policies, allowing users to manage permissions at a granular level. GitHub Enterprise also provides access control but is primarily based on user roles and teams. CodeCommit's IAM-based access control provides more flexibility and control over repository access.
Scalability and Performance: AWS CodeCommit is built on AWS infrastructure, which ensures scalability and high-performance capabilities. It can handle large code repositories and supports scalability to accommodate growing teams and projects. GitHub Enterprise's scalability and performance may be limited by the capacity of the local servers where it is installed.
Backup and Disaster Recovery: AWS CodeCommit automatically replicates repositories across multiple Availability Zones, providing redundancy and ensuring data availability in the event of a failure. It also allows for easy backup and restoration of repositories. GitHub Enterprise requires manual replication and backup processes to ensure data availability and disaster recovery.
In Summary, AWS CodeCommit offers a fully managed cloud-based version control service with seamless integration with AWS services, flexible pricing, fine-grained access control, scalability, and automatic backup and restoration capabilities. GitHub Enterprise, on the other hand, provides an on-premises version control solution with a fixed pricing structure, role-based access control, and limited scalability and disaster recovery options.
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 repos44
- IAM integration26
- Pay-As-You-Go Pricing24
- Amazon feels the most Secure20
- Repo data encrypted at rest19
- I can make repository by myself if I have AWS account11
- Faster deployments when using other AWS services11
- AWS CodePipeline integration8
- Codebuild integration6
- Does not support web hooks yet! :(6
- Cost Effective4
- No Git LFS! Dealbreaker for me2
- Elastic Beanstalk Integration2
- Integrated with AWS Ecosystem2
- Integration via SQS/SNS for events (replaces webhooks)1
- IAM1
- Issue tracker1
- Available in Ireland (Dublin) region1
- CodeDeploy Integration1
- CodeCommit Trigger for an AWS Lambda Function1
- Open source friendly1
- Only US Region1
- Ui0
Pros of GitHub Enterprise
- Expensive - $$$4
- Code security2
- CDCI with Github Actions2
- Both Cloud and Enterprise Server Versions available1
- Draft Pull Request1
- User experience0
Sign up to add or upvote prosMake informed product decisions
Cons of AWS CodeCommit
- UI sucks12
- SLOW4
- No Issue Tracker3
- Bad diffing/no blame2
- NO LFS support2
- No fork2
- No webhooks2
- Can't download file from UI1
- Only time based triggers1
- Accident-prone UI0
Cons of GitHub Enterprise
- $$$2