AWS Secrets Manager Posts

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=JOINNOW2403

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. Read more at New Section! Building Docker Images & ECS Rolling Deployments With AWS CodePipeline 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. Read more at 3 Ways for Environment Variables in AWS CodeBuild Buildspecs post.