DevOps Posts

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.

The most popular usage of Amazon CloudFront is to distribute static content such as images, videos or other objects existing in an Amazon S3 bucket. However, you can also use Amazon CloudFront to distribute your dynamic content such as a Ruby on Rails or PHP web application and benefit from the advantages of utilizing the globally distributed network infrastructure of AWS. In this blog post, I will talk about the advantages and the necessary configuration options for creating an Amazon CloudFront distribution for a dynamic web application. Read more at Serving Dynamic Websites with Amazon CloudFront post.

Today, encrypting data at rest is crucial for enhancing security of our applications. Besides, it might be a requirement for your compliance regulations. Whatever the reason is, it is a best practice to encrypt your Amazon Elastic Block Storage (EBS) volumes. In this post, I will show you how to encrypt an Amazon EBS volume using its integration with Amazon Key Management Service (KMS). Read more at Encrypting Amazon EBS Volumes post.

When you dockerize a Ruby on Rails application on AWS, it is essential to configure logging correctly to monitor application health. There are some tweaks to achieve this and I will briefly describe the process in this blog post.

Firstly, let’s make a brief introduction to Docker along with its deployment options on AWS. Read more at Configuring Ruby on Rails Logging for Docker on Amazon ECS or Fargate post.

As a passionate advocate for automation, I have been using AWS CloudFormation since the first day I started migrating my applications to AWS. I need to manage my time efficiently and should not repeat myself. By applying automation in infrastructure provisioning and keeping my architecture as a code, I can save, test, and re-use my work later.

Managing your infrastructure as code is one of the key DevOps practices, and AWS CloudFormation is your service on AWS to realize it. In this post, I explain 11 reasons for using AWS CloudFormation and automating the provisioning of your infrastructure.

Save your time, bring quality to your process by starting to prepare your CloudFormation templates today!