The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
The positive impact of AWS CodeCommit on my organization was significant, especially transitioning from Subversion (SVN), which was an outdated technology for repositories. It was a very hectic process to pull or push code in SVN due to too many rules.
Before using AWS CodeCommit, I utilized GitHub and SVN for these use cases.
The most valuable features of AWS CodeCommit include the least privilege access from IAM, where permissions are granted only for the specific repository the developer is working on, which allows for hundreds of repositories with controlled access per project. Additionally, we can connect a domain to the repositories for easier access via a web browser, and the integration with CodePipeline, CodeBuild, and CodeDeploy allows for seamless pulling from the repository, building and deploying products. Furthermore, there are connections to GitHub for those who use external repositories, and notification rules for commits and deployments keep the team informed through emails or Microsoft Teams, making it very helpful for any organization.
The branch management and pull requests structure helped improve collaboration among my team by establishing an organized hierarchy where the tech lead, as the main interactant with developers, has the full admin policy for PR approvals. Developers test in the dev environment and raise a PR which the tech lead can approve if the code is acceptable, merging it into the main or current branch for release. Before going to the main branch, the developer branch has a testing phase where it's vetted by the QA team according to company rules. Once QA approval is received, the tech lead merges the code into the main branch for release, whether it's small, mini, or major.
Understanding AWS CodeCommit was a hectic job for developers at first, while it was easier for the DevOps team. Even with access, they faced questions and difficulties navigating the service, indicating a need for better documentation. It would be beneficial if users knew how to navigate the documentation to get assistance. Furthermore, AWS CodeCommit has been discontinued, so those who created repositories before its discontinuation retain full access, while those who lost access should be assisted by AWS in connecting to GitHub or alternative solutions for easier migration. Although AWS services integrate more seamlessly, connecting third-party tools to AWS CodeCommit can be challenging, emphasizing the need for improved integration processes.
The distinct issue I wanted to improve while working with AWS CodeCommit related to the migration process. Moving from legacy repository services like SVN to AWS should ideally include a reliable migration plan to attract users rather than forcing them to seek other services. The migration was quite hectic initially, taking around two weeks. Easier integration and migration tools would have addressed these challenges and eliminated the issues with AWS CodeCommit.
I have been working with AWS CodeCommit for about one and a half years now.
The decision to switch from previous solutions like SVN and GitHub was made by our DevOps lead. Understanding the issues with SVN, which was old and likely to close, the transition was needed due to the cumbersome process of pushing and pulling code that involved many steps. While SVN required substantial setup and multiple commands to manage a simple task, AWS CodeCommit utilizes cloud technology, making it significantly easier to handle everything from authentication to repository management in a more streamlined fashion.
I have been exploring AWS WAF, VPC subnets, and Lambda lately.
I worked with AWS CodeCommit about six months ago, or maybe more.
The integration of AWS Identity and Access Management and AWS CodeCommit for managing access control was initially quite hard as I had to navigate various groups including developers, QA teams, admin teams, and the main AWS admin controller while also developing with Terraform. Once I established IAM groups, it became viable to manage permissions based on user groups rather than attaching policies to individual users, simplifying access control as users only receive permissions associated with their respective group like dev, QA, or tech leads, which streamlined the organizational structure while also focusing on specific repository access.
On a scale of 1-10, I rate AWS CodeCommit a 9.
I use AutomationEdge, and we also work with solutions from Microsoft Azure and AWS. We are using Azure OpenAI and AutomationEdge for AI solutions. For unstructured data, we are working on doing POCs, and we have completed POCs with true AI and AutomationEdge combination. We are trying to implement agentic solutions and agentic RPAs using true AI and AutomationEdge.
We utilize GitHub for fast tracking our implementations. We are using true AI for agentic solutions, and Core AI for chatbot.
It is very helpful, time saving, and user-friendly.
For code generation, we use GitHub mainly wherever required. We get a brief base code, and then we work on it, which enables a fast implementation process.
GitHub prompts you with just writing the prompt and it provides the code. If there are any errors, it helps find the solution for those errors. For code generation, it is a very helpful tool.
We have not used GitHub as a code repository. We have not used that feature of setup yet.
Sometimes we do not get the exact solution, and the suggested solution does not work, so GitHub could improve in that area. We have used GitHub mainly for the code generation part. That is the only area where we have used GitHub.
There can be some suggestions for improvement, though I am not heavily using this as the team mainly uses it.
We have been using it for one or two years.
We do whatever development is required in-house ourselves.
We have faced no issues with stability.
We have not used GitHub as a code repository. We have not used that feature of setup yet.
I have not contacted customer service.
Positive
For RPA, we are utilizing AutomationEdge only.
Initial setup is very simple.
Around 10-15 people on my team are using it.
I have not used that feature, so I am not sure.
I am not aware about the pricing, so I will not be able to give feedback.
We are utilizing AutomationEdge only for RPA. Currently, we are not using other solutions, but we are evaluating other platforms as well.
We are still working with AutomationEdge. We are not using Azure or AWS currently in my projects. I would rate GitHub eight or nine out of ten.
