Open Access Open Access  Restricted Access Subscription Access

“Cloud Formation (IaC)”: Deploying a Containerized Application on Cloud

Uddesh Piprewar, Shubham More, Vishal Lamsoge, Balwesh Puramkar, Gayatri Dandhare, Prof. Aditya Turankar

Abstract


Infrastructure as Code (IaC) is a practice that automates the deployment and management of infrastructure resources using machine-readable files, which describe the desired state of the desired state of the infrastructure. In this way, the infrastructure is treated as a code and is versioned, tested, and deployed like any other software artifact. Cloud providers offer IaC tools that facilitate the deployment of resources in a scalable and reproducible manner.

 

Containers have become the preferred way to package and deploy applications due to their portability, isolation, and scalability. Container orchestration platforms such as Docker simplify the management of containerized applications by automating the deployment, scaling, and monitoring of containerized workloads.

 

In this context, deploying a containerized application on the cloud involves defining the infrastructure resources required to support the application, such as virtual

machines, load balancers, and storage

 

 

 

 

volumes, using IaC tools. Once the infrastructure is defined, the containerized application is deployed on a container orchestration platform such as Docker, which manages the containers and their dependencies. This process enables the deployment of applications in a scalable, fault-tolerant, and cost-effective manner, while reducing the time and effort required to manage the underlying infrastructure.

 

In summary, the use of IaC and container orchestration platforms has revolutionized the way applications are deployed and managed on the cloud. These practices enable developers to focus on writing code rather than managing infrastructure, while ensuring that the infrastructure is deployed in a scalable, reproducible, and cost-effective manner.


Full Text:

PDF

References


IEEE 829-2008: This standard defines a comprehensive set of software documentation that includes specifications, test plans, and procedures. CloudFormation can be used to create, update, and delete infrastructure resources, which can be documented as a part of the software documentation.

IEEE 1471-2000: This standard defines an architectural framework for the development of software-intensive systems. CloudFormation can be used to define and provision the infrastructure resources required for the software-intensive systems.

IEEE 610.12-1990: This standard defines a set of terminology for software engineering. CloudFormation can be used to define and provision the infrastructure resources required for the software engineering process.

IEEE 610.12-1990: This standard defines a set of terminology for software engineering. CloudFormation can be used to define and provision the infrastructure resources required for the software.

IEEE 12207-2008: This standard defines the software life cycle processes. CloudFormation can be used to automate the provisioning of infrastructure resources throughout the software development life cycle.

IEEE Std 828-2012 - This standard provides guidance on the development of software documentation, including requirements, design, and testing documentation. When using CloudFormation, it is important to document your templates and workflows to ensure that your

infrastructure is well-understood and maintainable.


Refbacks

  • There are currently no refbacks.