AWS CloudFormation Posts - Page 3

The Order of Resource Creations on AWS CloudFormation

AWS CloudFormation resource creations order

In an AWS CloudFormation template, you define independent resources or resources that are implicitly dependent; in other words, referencing other resources. For instance, you can define an Amazon EC2 instance and a security group. Then, you might choose to attach the security group to the EC2 instance or not. In these two cases, AWS CloudFormation organizes the order of the resource creations 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 is 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 to add your custom dependencies in a template. Read more at The Order of Resource Creations on AWS CloudFormation post.

11 Reasons to Use AWS CloudFormation for Provisioning Your Architecture

11 Reasons to Use AWS CloudFormation for Provisioning Your Architecture

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!

Read more at 11 Reasons to Use AWS CloudFormation for Provisioning Your Architecture post.

Provisioning Custom AWS CloudFormation Resources With AWS Lambda Functions

AWS CloudFormation is the foundation of operational excellence on AWS. We code our infrastructure as JSON or YAML templates and test it as much as we need before deploying to production. We manage our infrastructure as code.

However, some new AWS resources may not be supported by AWS CloudFormation at the time they are launched. As of today, an example of this is the Elastic GPU resource. The solution is to define a custom CloudFormation resource and attach it to an AWS Lambda function which launches these resources. The Lambda function should also be in the same template. So let’s talk about how to do this in this blog post. Read more at Provisioning Custom AWS CloudFormation Resources With AWS Lambda Functions post.