Need advice about which tool to choose?Ask the StackShare community!

AWS CodeCommit

327
819
+ 1
193
Beanstalk

87
267
+ 1
51
Add tool

AWS CodeCommit vs Beanstalk: 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, Beanstalk is detailed as "Private code hosting for teams". A single process to commit code, review with the team, and deploy the final result to your customers.

AWS CodeCommit and Beanstalk belong to "Code Collaboration & Version Control" category of the tech stack.

Some of the features offered by AWS CodeCommit are:

  • Collaboration
  • Encryption
  • Access Control

On the other hand, Beanstalk provides the following key features:

  • Setup and manage repositories- Import or create Subversion and Git repositories that are instantly available to your team.
  • Invite team members, partners & clients- Restrict access to certain repos and provide read-only or full read/write permissions.
  • Browse files and changes- Every version of every file you’ve committed to Beanstalk is just a click away. See a timeline of who made changes and view the differences between revisions. Syntax highlighting for over 70 languages.

"Free private repos" is the primary reason why developers consider AWS CodeCommit over the competitors, whereas "Ftp deploy" was stated as the key factor in picking Beanstalk.

According to the StackShare community, AWS CodeCommit has a broader approval, being mentioned in 25 company stacks & 17 developers stacks; compared to Beanstalk, which is listed in 21 company stacks and 8 developer stacks.

Advice on AWS CodeCommit and Beanstalk

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.

  1. Is it a good idea to migrate from Bitbucket to AWS Codecommit?
  2. 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?
See more
Replies (1)
Sinisha Mihajlovski
Design Lead | Senior Software Developer · | 1 upvotes · 289.1K views
Recommends

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of AWS CodeCommit
Pros of Beanstalk
  • 44
    Free private repos
  • 26
    IAM integration
  • 24
    Pay-As-You-Go Pricing
  • 20
    Amazon feels the most Secure
  • 19
    Repo data encrypted at rest
  • 11
    Faster deployments when using other AWS services
  • 11
    I can make repository by myself if I have AWS account
  • 8
    AWS CodePipeline integration
  • 6
    Codebuild integration
  • 6
    Does not support web hooks yet! :(
  • 4
    Cost Effective
  • 2
    No Git LFS! Dealbreaker for me
  • 2
    Integrated with AWS Ecosystem
  • 2
    Elastic Beanstalk Integration
  • 1
    Integration via SQS/SNS for events (replaces webhooks)
  • 1
    IAM
  • 1
    Open source friendly
  • 1
    Only US Region
  • 1
    Available in Ireland (Dublin) region
  • 1
    CodeDeploy Integration
  • 1
    Issue tracker
  • 1
    CodeCommit Trigger for an AWS Lambda Function
  • 0
    Ui
  • 14
    Ftp deploy
  • 9
    Deployment
  • 8
    Easy to navigate
  • 4
    Code Editing
  • 4
    HipChat Integration
  • 4
    Integrations
  • 3
    Code review
  • 2
    HTML Preview
  • 1
    Security
  • 1
    Blame Tool
  • 1
    Cohesion

Sign up to add or upvote prosMake informed product decisions

Cons of AWS CodeCommit
Cons of Beanstalk
  • 12
    UI sucks
  • 4
    SLOW
  • 3
    No Issue Tracker
  • 2
    Bad diffing/no blame
  • 2
    NO LFS support
  • 2
    No fork
  • 2
    No webhooks
  • 1
    Can't download file from UI
  • 1
    Only time based triggers
  • 0
    Accident-prone UI
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is AWS CodeCommit?

    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.

    What is Beanstalk?

    A single process to commit code, review with the team, and deploy the final result to your customers.

    Need advice about which tool to choose?Ask the StackShare community!

    Jobs that mention AWS CodeCommit and Beanstalk as a desired skillset
    What companies use AWS CodeCommit?
    What companies use Beanstalk?
    See which teams inside your own company are using AWS CodeCommit or Beanstalk.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with AWS CodeCommit?
    What tools integrate with Beanstalk?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to AWS CodeCommit and Beanstalk?
    GitHub
    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
    GitLab
    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.
    Bitbucket
    Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
    GitHub Enterprise
    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.
    SVN (Subversion)
    Subversion exists to be universally recognized and adopted as an open-source, centralized version control system characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations.
    See all alternatives