{"id":18308,"date":"2015-03-30T16:36:55","date_gmt":"2015-03-30T11:06:55","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=18308"},"modified":"2020-11-24T12:12:55","modified_gmt":"2020-11-24T06:42:55","slug":"using-aws-cloudformer-to-create-template-of-existing-infrastructure","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/using-aws-cloudformer-to-create-template-of-existing-infrastructure\/","title":{"rendered":"Using AWS CloudFormer to create template of existing infrastructure"},"content":{"rendered":"

AWS CloudFormer is a template creation tool and it creates AWS CloudFormation template from our existing resources in AWS account. We can select any supported AWS resources<\/a> that are running in our account, and CloudFormer creates a template in an Amazon S3 bucket. We will be using AWS CloudFormer to create template of existing infrastructure.<\/strong><\/p>\n

AWS CloudFormation<\/h3>\n

AWS CloudFormation can be used with sample templates\u00a0or our own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run an application. We don\u2019t need to figure out the order of provisioning services (or the subtleties of making those dependencies work). CloudFormation takes care of this for you. After the resources are deployed, we can modify and update them in a controlled and predictable way, this applies version control to our infrastructure the same way as we can do with software.
\nWe can deploy and update a template and its collection of resources (called a stack) by using the AWS<\/a> Console (or AWS CLI or APIs). CloudFormation is available at no additional charge, and we are charged only for the resources needed to run your applications.<\/p>\n

In other words, CloudFormation<\/strong> is used create a infrastructure through a template (JSON script):<\/p>\n

1) Available on AWS website for different use-cases e.g.two servers with apache installed attached to a load balancer.<\/p>\n

2) Customized script as per our requirement.<\/p>\n

CloudFormer<\/strong> automates our work by managing selected resources that have dependent resources (for example, an Amazon EC2 instance is associated with an EC2 security group), the tool will automatically select any dependent resources. We can override any of the pre-selected resources or add other resources as necessary . We have full control of the resources to be included in our template. Names are chosen based on the existing resource names (we can edit the names that will be included in the template and we can add output parameters based on the attributes available for any of the resources. The template can be uploaded to a S3 bucket and launched directly via the AWS CloudFormation stack creation wizard. (reverse of CloudFormation)<\/p>\n

The CloudFormer tool<\/strong> is used to create a starting point of template. Once created, we can customize it, as following:<\/p>\n