AWS CodeBuild vs. HashiCorp Packer

I enjoy it - very cool service. I would say give it a try.

Incentivized

We use packer to generate new machine images for multiple platforms on every change to our Configuration Management tools like Chef/Puppet/Ansible It's act single tool for Image building for Multi-provider like AWS/Azure/GCP Helps to achieve Dev/Prod Parity Packer itself doesn't have a state like Terraform. You can't do packer output AMI ID. If you have a scenario where you want to maintain the state for images it would be tough to manage via Packer.

Incentivized

• Customization
• Do code builds within a schedule or when the source code changes
• Only pay for the build time used

Incentivized

• Multi-provider portability
• Greater testability
• Super fast infrastructure deployment

Incentivized

• It was difficult to create a branching strategy with GitHub. We had everything running from main, but in a true devops environment, we would like to incorporate a true branching strategy.
• I would like to share build projects with each AWS account we utilize versus creating a build project in each account. It will allow us consistent deployments across the board.
• The error logs are natively in AWS, but when developers do not have access, there is no way for them to view error logs for maintenance other than an admin who has access to share the error logs.

Incentivized

• Manageability
• Manageability
• Manageability

Incentivized

We are happy with the use of Packer in our organization. Apart from manageability, I don't find any other drawback with Packer.

Incentivized

It is a highly usable, well integrated CI/CD service, patricularly for AWS-centric organizations. It is a strong balance between simplicity and flexibility. Security was integrated with AWS Secrets Manager allowing secrets to be retrieved dynamically - a huge usability win for us. I did not enjoy the manual build for each environment

Incentivized

It's best for building Image with many features and benefits.

Incentivized

I only once required support and it was very smooth.

Incentivized

I haven't found any issue in Implementation that itself describes how well this tool is built.

Incentivized

AWS CodeBuild provides the option to fully implement the build in the cloud without wasting your local resources (computer and network) providing independence to developers to invest those resources in other processes. It also provides a robust platform with a lot of customizations or just a script for each language.

Incentivized

There are lot of tools in market which does the job for Image creation but all of them are not complete Machine/Image as a code. All other alternatives can create Image partially. Main reason for selecting Packer are Packer is lightweight, portable, and command-line driven Packer helps keep development, staging, and production as similar as possible. Packer automates the creation of any type of machine image Multi-provider portability is the feature to die for

Incentivized

• It has a positive ROI

Incentivized

• Super fast infrastructure deployment
• Quick turnaround of infrastructure in multiple cloud using single tool.
• Increase productivity by reducing time in infrastructure building.

Incentivized