My recommendation for AWS CodeBuild to make it better for the next release would be something within AWS CodeBuild which can support the repository functions as well. It may not be as powerful as GitHub Actions, but it provides a very competitive price compared to GitHub Actions. GitHub Actions, if you want to use the YML CI/CD pipeline, gives a free tier of around three thousand hours per month. AWS CodeBuild is a little more expensive than that. However, if it supports the repository function as well along with it, then it will be a complete package. Everything would be in AWS, including the code versioning, code commit to the code infrastructure, to the code database, to the networking, and how the applications are accessed. Everything would be in one place, which would be very helpful. I believe AWS CodeBuild is a bit expensive because GitHub provides around three thousand minutes free, plus it has the free repository function as well. At the enterprise level, it charges maybe around nineteen dollars per user, though I do not remember exactly. In terms of AWS CodeBuild, I believe it is a bit expensive because it is providing only the deployment features. It is not providing the repository. In that comparison, I would say it is a little bit expensive.
The servers used for macOS and iOS builds are limited in availability, operating only in US East 1 and East 2, and US West 1 and West 2. This geographical limitation causes latency issues and extended build times for regions such as India, impacting production efficiency. However, other server types are available across all regions without such limitations.
AWS Devops Support Engineer at a recruiting/HR firm with 11-50 employees
Real User
Top 10
Apr 28, 2025
There is room for improvement in making AWS CodeBuild available on Windows servers in the Mumbai region. Multiple clients have faced issues with pricing. After migrating from Azure ( /products/microsoft-azure-reviews ) to EC2 ( /products/amazon-ec2-reviews ), they were unexpectedly charged 100,000 rupees because the pricing details were not clearly visible. Displaying costs alongside the EC2 ( /products/amazon-ec2-reviews ) options could help clients avoid such billing surprises.
Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds.
Cloud System Specialist at a financial services firm with 51-200 employees
Real User
Top 5
Aug 20, 2024
For improvement, I'd suggest more build instance-type options. There's a big jump from 15 gigabytes of RAM to 150, and I'd like something in between as the larger option is too expensive for our needs.
While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected. Although conditions were functioning correctly, the lack of support for looping hindered my ability to execute certain tasks efficiently.
The product must provide more integrations. It is a replica of Jenkins. We have a management overhead. When I build artifacts stored outside the S3 bucket, it will have additional charges on the storage volumes. If we use S3 buckets regularly, it is fine. However, when we store somewhere else, it will be an issue. There is no persistent storage or preservation of workspace between the builds. We must fix the dependencies every time, even if the dependencies are the same. It is unnecessary.
AWS CodeBuild provides automated build services with seamless AWS service integrations and third-party tools, supporting multiple programming languages. It features serverless architecture, facilitating flexible and efficient workflows.AWS CodeBuild enables automation of builds through webhooks and integrates smoothly with platforms like GitLab and Jenkins. Its architecture allows multiple concurrent builds, enhancing productivity and speed. With features like CloudWatch logging and IAM...
My recommendation for AWS CodeBuild to make it better for the next release would be something within AWS CodeBuild which can support the repository functions as well. It may not be as powerful as GitHub Actions, but it provides a very competitive price compared to GitHub Actions. GitHub Actions, if you want to use the YML CI/CD pipeline, gives a free tier of around three thousand hours per month. AWS CodeBuild is a little more expensive than that. However, if it supports the repository function as well along with it, then it will be a complete package. Everything would be in AWS, including the code versioning, code commit to the code infrastructure, to the code database, to the networking, and how the applications are accessed. Everything would be in one place, which would be very helpful. I believe AWS CodeBuild is a bit expensive because GitHub provides around three thousand minutes free, plus it has the free repository function as well. At the enterprise level, it charges maybe around nineteen dollars per user, though I do not remember exactly. In terms of AWS CodeBuild, I believe it is a bit expensive because it is providing only the deployment features. It is not providing the repository. In that comparison, I would say it is a little bit expensive.
The servers used for macOS and iOS builds are limited in availability, operating only in US East 1 and East 2, and US West 1 and West 2. This geographical limitation causes latency issues and extended build times for regions such as India, impacting production efficiency. However, other server types are available across all regions without such limitations.
There is room for improvement in making AWS CodeBuild available on Windows servers in the Mumbai region. Multiple clients have faced issues with pricing. After migrating from Azure ( /products/microsoft-azure-reviews ) to EC2 ( /products/amazon-ec2-reviews ), they were unexpectedly charged 100,000 rupees because the pricing details were not clearly visible. Displaying costs alongside the EC2 ( /products/amazon-ec2-reviews ) options could help clients avoid such billing surprises.
We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better.
I faced some challenges while using CodeBuild. I would like to see some improvements in certain limitations of the product.
Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds.
For improvement, I'd suggest more build instance-type options. There's a big jump from 15 gigabytes of RAM to 150, and I'd like something in between as the larger option is too expensive for our needs.
While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected. Although conditions were functioning correctly, the lack of support for looping hindered my ability to execute certain tasks efficiently.
They can further improve the integration of the Bitbucket for CodeBuild.
The product must provide more integrations. It is a replica of Jenkins. We have a management overhead. When I build artifacts stored outside the S3 bucket, it will have additional charges on the storage volumes. If we use S3 buckets regularly, it is fine. However, when we store somewhere else, it will be an issue. There is no persistent storage or preservation of workspace between the builds. We must fix the dependencies every time, even if the dependencies are the same. It is unnecessary.