AWS CodeBuild Posts

AWS CodeArtifact enables you to store your custom packages or fetch packages from public package registries and use them in your software development process. If you use AWS CodeBuild to build your code, you can make CodeBuild retrieve the packages required for your build or test commands from your CodeArtifact repository on AWS instead of public Internet registries.

In this post, I will introduce you to AWS CodeArtifact and provide an example of using it with AWS CodeBuild to build an Angular application.

Continue reading the Using AWS CodeArtifact with AWS CodeBuild: An Angular Build Example blog post.

I am excited to share our newest section in my Udemy bestseller AWS CodePipeline Step by Step course, Building Docker Images & ECS Rolling Deployments With AWS CodePipeline.

If you’ve not joined yet, for the next five days, you can join this course with a best-price coupon special to the launch of the new section using the link below:

https://www.udemy.com/course/aws-codepipeline-step-by-step/?couponCode=JOINNOW2411

Our newest section focuses on building your Docker images, publishing them to Docker Hub or Amazon ECR with AWS CodePipeline and AWS CodeBuild, and deploying them to Amazon ECS as rolling deployments** using the direct integration of CodePipeline with ECS.

Continue reading the New Section! Building Docker Images & ECS Rolling Deployments With AWS CodePipeline blog post.

Today, applying CI/CD is one of the most crucial DevOps practices. CI means Continous Integration, whereas CD can be applied as either Continuous Development or Continuous Deployment. Sometimes the terminology may seem confusing and people talking about them often assume that you know them from the beginning. So, as a developer applying CI/CD for years and having launched a course about the native CI/CD solution of AWS, AWS CodePipeline, I may help you understand these DevOps concepts. In this post, I will discuss what CI and CD practices mean and explain their differences.

Continue reading the CI vs. CD: What are Continuous Integration, Delivery or Development? blog post.

AWS CodePipeline provides AWS CloudFormation Create or update stack and Create or replace change set action types to deploy your CloudFormation stacks from your pipeline. If you have joined my AWS CodePipeline Step by Step course, you would remember our example there. We automatically create a staging stack from a CloudFormation template before the manual approval action in our pipeline.

However, AWS CodePipeline’s CloudFormation action types only create stacks from deployable stack templates. Therefore, you cannot deploy your CloudFormation nested stacks with local path template definitions directly without packaging and uploading them to an S3 bucket first. In this post, I will talk about achieving this on an AWS CodePipeline pipeline using AWS CodeBuild.

Continue reading the Deploying CloudFormation Nested Stacks With AWS CodePipeline & AWS CodeBuild blog post.

AWS CodeBuild is the serverless build service of AWS, and until now, I covered various ways of using it in my previous posts. Today, I would like to talk about how to define and use environment variables in your build specification files or, in other words, buildspecs. In a build project, you can assign plain texts to your environment variables, read parameters from AWS Systems Manager Parameter Store, or retrieve secrets from AWS Secrets Manager. I will give examples to each.

Besides, you can also use AWS CodeBuild with AWS CodePipeline as a part of a CI/CD pipeline. We discuss how to do this in my AWS CodePipeline Step by Step course. Therefore, I will also give an example of exporting an environment variable from a build to be able to use it in a later pipeline action.

Continue reading the 3 Ways for Environment Variables in AWS CodeBuild Buildspecs blog post.