Recommendations to others considering AWS CodeBuild:
If you need regular builds, it may be beneficial to set up artifact/dependency caching at CodeBuild project level in order to reduce build time.
Note that private repositories (e.g. on GitHub) may not be supported.
If you use S3 (or any other storage-as-a-service solution) as the build target, make sure you have a mechanism to clean up old build artifacts as otherwise you'll end up with lots of garbage. Review collected by and hosted on G2.com.
What problems is AWS CodeBuild solving and how is that benefiting you?
Performing builds in our own serverless IDE Sigma, on behalf of our users.
It means we don't have to manage or pay for a dedicated build server, and users can build their projects right within their own AWS accounts without disclosing their sources to a third party service.
The free tier pretty much eliminates user-side costs, and we can ask CodeBuild to directly upload the build artifacts to S3, which we can then use in the deployment process. Review collected by and hosted on G2.com.