When should I use CodeBuild Lambda compute?

Question

I noticed CodeBuild recently launched a new Lambda Compute feature that provides faster build times. However, the doc also mentions that the feature has some limitations like max memory and timeout durations

I'm trying to understand whenCodeBuild Lambda compute would be the best option. What are some key factors to consider when deciding between Lambda vs EC2 for CodeBuild? What types of workloads or use cases work best with Lambda compute?

Accepted Answer

Great question! As you mentioned, some of the main advantages with CodeBuild Lambda are faster build times and lower costs compared to traditional EC2 builds. With per-second billing, CodeBuild Lambda can be cost-effective for shorter, smaller builds with runtimes lower than the 15 minute Lambda timeout duration.

I have found that CodeBuild Lambda works great for smaller, lightweight projects or scripts. For example, I am currently using it to run linting/unit tests for my Node.JS application. I have also used it in the past with [AWS SAM](https://aws.amazon.com/serverless/sam/) to quickly build, test, and deploy code to AWS infrastructure. While it still works with traditional build tasks, CodeBuild lambda also works great with operational tasks beyond builds such as generating reports, sending notifications, or managing deployments.

For more information, check out the [CodeBuild Lambda samples page](https://docs.aws.amazon.com/codebuild/latest/userguide/lambda-samples.html), as it has some small projects to get you started using CodeBuild Lambda.

When should I use CodeBuild Lambda compute?

関連するコンテンツ