Shulou(Shulou.com)06/03 Report--

Related concepts of Cloudformation

AWS cloudformation is a typical infrastructure, namely code service. Invokes and orchestrates the resources of Amazon cloud services by writing templates. Cloudformation can greatly help DevOps improve productivity, reduce duplication of effort, configure and deploy related services, and spend more energy on applications.

Summarize the advantages of cloudformation service by citing the AWS official website https://docs.aws.amazon.com:

Simplify infrastructure management, fast replication infrastructure, easily control and track changes at the infrastructure layer

Deployment business: traditional environment VS AWS cloud environment

Image above: the traditional environment is mainly hardware, procurement and deployment is time-consuming, capital, venues, equipment and other resource costs and a lot of waste can be found everywhere, unable to pay on demand. It takes months for a traditional hardware data center to go from deployment to formal operation! In the later stage, operation and maintenance have to face all kinds of equipment failures and safety problems.

In AWS cloud environments, hardware devices in traditional environments are virtualized / logical. The deployment is flexible and convenient, the capital cost is low, there is no space demand, and the use is paid on demand. Infrastructure construction can be completed with a few mouse clicks, and the minute-level data center on the cloud takes time from deployment to usage. Various feature advantages of AWS cloud, such as auto-recovery, allow users to minimize problems such as underlying hardware failures. From the capital expenditure to the rich aspects of technical support, kill the traditional hardware environment data center.

Deploy business: do not use cloudformation VS, use cloudformation

Image above: when cloudformation is not deployed, it is assumed that a business requires several service components of EC2+mysql+S3+pipeline. Users need to deploy in the Development environment first, then deploy to the Staging environment after passing the test, and then deploy to the Production environment after passing the test. The same work needs to be repeated three times, which is just a single business. Although this manual deployment is much faster and flexible than traditional hardware data centers, it still does not meet the requirements of efficient DevOps work. Real DevOps on AWS tends to take the next approach.

Image above: the cloudformation template deploys the business way, and arranges the resources of the AWS cloud platform through pre-written templates in Yaml or Json language. Declare and invoke resources such as EC2+mysql+S3+pipeline in a template. The deployment of the template in the Development environment can be completed in a few minutes, and when deployed in the Staging and Production environments after the test is completed, there is no need to re-build various infrastructure modification configuration files as before, such a large and repetitive and time-consuming work, but simply call the prepared cloudformation template again.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.