DevOps Posts

If you use Bitbucket for your private Git repositories, you cannot use AWS CodePipeline to create a CI/CD pipeline. Because CodePipeline does not support Bitbucket as a source repository. However, if you still want to use AWS developer tools to automate your builds and deployments, you have an alternative. AWS CodeBuild supports Bitbucket integration as source allowing to trigger builds after push requests to a Bitbucket repository by publishing it as a webhook to it.

By the way, Angular is one of the most popular frontend frameworks and you can deploy your Angular projects in a serverless manner. So it can be reliable, scalable and cost-effective by design. You can build your code, upload to an Amazon S3 bucket and distribute it via Amazon CloudFront.

In this post, I will make an example of using a Bitbucket repository for your Angular projects and triggering builds on AWS CodeBuild after pushing your changes to it. Then your AWS CodeBuild project can build your Angular code and deploy it to an Amazon S3 bucket making it ready for distributing via CloudFront. Read more at Building Angular Apps with AWS CodeBuild upon Bitbucket Pushes post.

Having a Ruby on Rails background, I got excited to try Ruby to code my AWS Lambda functions when its support for AWS Lambda was announced at Re:Invent 2018. Finally, to try Ruby on AWS Lambda, I developed a simple API using AWS Serverless Application Model (SAM) to access an Amazon RDS MySQL database. I wanted to compare it with my experiences of doing this with Python and Node.js.

Although it may seem simple, installing mysql2 gem as a dependency proved itself to be challenging than others, because it has native extensions and depends on the environment you use bundler. As always, Docker simplifies our job by providing a similar environment that our AWS Lambda function runs inside.

In this post, I will make an introduction to AWS SAM CLI and using Ruby for AWS Lambda functions. Let’s begin! Read more at Creating a Serverless API Using SAM CLI and Ruby for AWS Lambda to Access Amazon RDS MySQL post.

AWS CloudFormation provides a handful of pseudo parameters which you can use to increase the reusability of your templates along with your template conditions and parameters. One of them is the AWS::NoValue parameter which acts like the null value in programming languages.

In this post, I will talk about some examples of its use cases.

I am happy to announce that my new course, AWS CloudFormation Step by Step: Beginner to Intermediate, is now live on Udemy.

In this post, I want to introduce you with this new course. I will talk about the topics, what you will learn by taking it as well as the structure of the course. In addition, I will also share a free coupon that will be valid for a limited time with the followers of this blog. Read more at My New Course AWS CloudFormation Step by Step: Beginner to Intermediate is Live! post.

In an AWS CloudFormation template, you define independent resources or resources that are implicitly dependent, in other words, reference other resources. For instance, you can define an EC2 instance and a security group. Then, you might choose to attach the security group to the instance or not. In these two cases, AWS CloudFormation organizes the order of the creation of resources differently.

In addition, you might have another resource such as an Amazon SNS topic in the same template which you might want to provision after your EC2 instance created. Maybe you have an explicit dependency between them.

In this blog post, I will talk about how AWS CloudFormation handles the order of creation for independent or implicitly dependent resources. I will also explain how you can add your own dependencies in a template, as well. Read more at The Order of Resource Creations on AWS CloudFormation post.