Likelihood to Recommend I think AWS CodePipeline is a great tool for anyone wanted automated deployments in a multi-server/container AWS environment. AWS also offers services like Elastic Beanstalk that provide a more managed hosting & deployment experience. CodePipeline is a good middle ground with solid, built-in automation with enough customizability to not lock people into one deployment or architecture philosophy.
Read full review The thing I mentioned earlier where we're constantly dealing with federal regulations or new agents that they want us to install and deploy and just getting those out in a consistent manner in a canned installation via Playbook is ideal
Read full review Pros It is reliable and works without errors It integrates well with our repository and all other AWS functions as well as our end database Read full review Makes it easy to create and share automation in one central hub. Ansible content collections give me the ability to reuse code, making it rapid to carry out complex IT processes. Event-driven automation allows me to reduce manual tasks: it is rapid to know which action to take and respond automatically by receiving events from external apps automatically. Read full review Cons Ease of use - things like CircleCI or other tools are a bit easier to learn. Ability to build from more sources. Read full review Workflows should have more flexible paths than just success or failure. The upgrade process can be challenging with differences in security and environment. There is an opportunity to add CICD functionality into the tool. For development, it would be nice to have the option of editing a repo directly from AAP to allow quick tests/reruns. Then, allow it to push the updates back or create a new branch/PR in GitHub. The RBAC is good but could use improvements. One example would be an option that allows admins to assume the access of another user to validate it works as expected. Read full review Likelihood to Renew We are deploying Ansible at all levels of the organization
Read full review Usability Overall, I give AWS Codepipeline a 9 because it gets the job done and I can't complain much about the web interface as much of the action is taking place behind the scenes on the terminal locally or via Amazon's infrastructure anyway. It would be nicer to have a better flowing and visualizable web interface, however.
Read full review the yaml is easy to write and most people can be taught to write basic playbooks in a few weeks
Read full review Performance Our pipeline takes about 30 minutes to run through. Although this time depends on the applications you are using on either end, I feel that it is a reasonable time to make upgrades and updates to our system as it is not an every day push.
Read full review Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
Read full review Support Rating We didn't need a lot of support with AWS CodePipeline as it was pretty straightforward to configure and use, but where we ran into problems, the AWS community was able to help. AWS support agents were also helpful in resolving some of the minor issues we encountered, which we could not find a solution elsewhere.
Read full review There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
Read full review Implementation Rating I spoke on this topic today!
Read full review Alternatives Considered CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for
Beanstalk , which is often used as a deployment target in relation to CodePipeline.
CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via
Beanstalk .
Jenkins is open source and not a native AWS service, that is its primary differentiator.
Jenkins can also be used as a supplement to CodePipeline.
Read full review AAP doesn't truly stack up against any of the products mentioned except for
Aria Automation. But, it is extensible and open and has a lower cost to entry.
Read full review Return on Investment CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing. CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch. CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually. Read full review Red Hat Ansible Automation Platform offers automation and ML tools that allow me to automate complex IT tasks. Through automation analytics, it is seamless to gain full visibility into automation performance allowing me to make informed decisions. Red Hat Ansible Automation Platform allows me to move rapidly from insights to action. Creating and sharing automation content in one place unify a team in one place hence enhancing real-time collaboration. Read full review ScreenShots