My experience with AWS CodeBuild

Rating: 8 out of 10

October 22, 2025

Use Cases and Deployment Scope

Our organization implemented AWS CodeBuild to deploy as a central component of my organization's database deployment automation pipeline, particularly for Liquibase schema and data change management across multiple AWS environments.

AWS CodeBuild was integrated into a broader CI/CD ecosystem that included GitHub Enterprise as a source, AWS Secrets Manager for credential management and S3 for artifact storage and logging.

Pros

AWS CodeBuild allowed seamless integration across AWS Services - allowed us to pull binaries directly from s3, fetching secrets etc.
Wrote detailed logs creating immutable audit trails that helped from a technical and compliance perspective
Automated a repeatable build and deployment process. We ran updates automatically based on environment allowing pipelines to reuse the same build template with different environment parameters.

Cons

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.

Likelihood to Recommend

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

Marrsail Bailey

Technical Architect Specialist in Engineering at Accenture Federal Services (10001 employees)

Vetted Review

1 year of experience

Verified on LinkedIn

Great Platform

Rating: 9 out of 10

Incentivized

August 17, 2021

Use Cases and Deployment Scope

It is used by all the organization (development team). We use it for compiling the code and running tests. It allows customization of the builds, so when a team or project needs to do a stack for something specific, it helps a lot. Most of the builds are for testing purposes.

Pros

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

Cons

Sometimes it runs an outage and developers don't know why. We have to contact DevOps most of the time.
Sometimes it is slow

Likelihood to Recommend

It is really good for building projects in the cloud. If you try to do build the project first locally and then push that stack to the cloud it could take a lot of time. In this way, it also consumes a lot of resources in the computer and in the network.

Manuela Jacqueline Mercado Rodríguez

Senior Full Stack Developer in Engineering at Intellisys D. Corp. (51-200 employees)

Vetted Review

1 year of experience

View profile

My experience with AWS CodeBuild

Rating: 8 out of 10

Incentivized

October 22, 2025

Use Cases and Deployment Scope

Pros

AWS CodeBuild allowed seamless integration across AWS Services - allowed us to pull binaries directly from s3, fetching secrets etc.
Wrote detailed logs creating immutable audit trails that helped from a technical and compliance perspective
Automated a repeatable build and deployment process. We ran updates automatically based on environment allowing pipelines to reuse the same build template with different environment parameters.

Cons

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.