Enhancing Efficiency through Infrastructure Automation: An In-depth
Analysis of Infrastructure as Code (IaaC) Tools
Milandeep Kour Bali 1st
Department of Computer Science and
Engineering
Apex Institute of Technology (CSE)
Chandigarh University
Gharaun,Mohali,India
milandeepbali@gmail.com
Abstract— A powerful Infrastructure as Code (IaC)
management and deployment are automated by a
systemVirtual machines and networks are vital infrastructure
components that cannot be overlooked. By relying on
configuration files as the single source of truth, resources are
consistently deployed with the same configurations,
eliminating human error and discrepancies caused by
individual settings. Additionally, IaC tools ensure that the
infrastructure remains in the desired state, promptly alerting
relevant parties to any deviations. Another significant benefit
of IaC is its ability to simplify tracing and auditing processes.
Since all operations are stored in configuration files, it
becomes easy to track changes and facilitate compliance.
Testers can execute scripts on replicated production
environments, while developers can quickly set up test
environments to evaluate new application features.
Keywords— Iaac, Api, Aws, Azure, Terraform, Cloud
Computing, DevOps
I. INTRODUCTION
Infrastructure as code (IaC) is a technique of defining and
deploying infrastructure, such as networks, virtual machines,
load balancers, and connection topologies, using the DevOps
methodology and versioning with a descriptive model. An IaC
model creates the same environment each time it is deployed, just
as the same source code creates the same binary every time.
Environment drift in release pipelines is a challenge that IaC
evolved to address. Teams must independently maintain
deployment environment parameters without IaC. Each setting
eventually turns into a "snowflake," a singular configuration that
cannot be automatically duplicated [2]. Deployment problems
may be brought on by environment inconsistency. Manual
operations that are prone to error and difficult to track are used in
infrastructure administration and maintenance. By using well
documented code in formats like JSON to represent intended
environment states, IaC minimizes manual configuration and
upholds consistency. IaC enables repeatable infrastructure
installations that avoid runtime problems brought on by errant
configuration changes or missing dependencies. Target
environments are configured by release pipelines using version
configuration models and environment descriptions. The team
modifies the source rather than the target while making
modifications.
Ranjan Walia 2nd
Department of Computer Science and
Engineering
Apex Institute of Technology (CSE)
Chandigarh University
Gharaun,Mohali,India
ranjanwalia@gmail.com
An essential IaC principle is idempotence, or the capacity of a
given operation to consistently yield the same outcome.
Regardless of the environment's beginning state, a deployment
command always puts the target environment into the same
configuration. Either the existing target is automatically
configured, or the old target is discarded, and a new environment
is created, to achieve idempotency [10]. If at all practicable, IaC
ought to use declarative definition files. An environment's
required components and configuration are described in a
definition file, but the method for achieving that configuration is
not always specified. Various platforms can open files in the
YAML, JSON, and XML formats. With the help of infrastructure
provisioning, IaC addresses numerous typical issues. Treating
infrastructure, the same way developers address code is a core
DevOps principle.
There is a specific format and grammar for the application code.
Applications cannot be made if the code is not written in
accordance with the rules of the programming language. A version
management or source control system that keeps track of changes
made to the code as well as bug fixes stores the code. We anticipate
a consistent application to be produced when code is generated or
built into apps, and that the build will be repeatable and reliable.
Developing infrastructure with the same rigor as application code
requires the use of infrastructure as code. The same manner that
application code is kept in a source control system like AWS Code
Commit, all configurations should be defined declaratively. The
use of infrastructure as code should be supported by the
provisioning, orchestration, and deployment of infrastructure.
Historically, provisioning infrastructure has been done manually
and with scripts. These scripts were occasionally kept in version
control databases or meticulously described in text files or
runbooks. Often, the person executing these scripts or carrying out
the instructions in the run books is not the same person who wrote
them. These runbooks or scripts could potentially prevent
deployments if they are not regularly updated. Because of this, the
development of new settings is not necessarily dependable,
repeatable, or consistent [12]. Amazon, in contrast, offers a
DevOps-focused approach to building and maintaining
infrastructure. Amazon offers services that make it possible to
build, deploy, and maintain infrastructure in a programmatic,
descriptive, and declarative manner, much to how software
developers write application code. These services offer accuracy,
precision, and dependability. The Amazon services covered in this
article serve as the foundation for many higher, level AWS
DevOps ideas and practices and are essential to a DevOps
approach.

Fig:1 Popularity of Infrastructure as Code Tools
II. RELATED WORK
A. Dalvi et al. [1] To determine the trends, tools, and problems
in DevOps research, the authors thoroughly examined 294 peer
reviewed publications published between 2010 and 2020.The
authors cited a number of DevOps research trends, including
growing use of automation, microservices, and
containerization. They also discovered that more people are
becoming interested in adopting DevOps for applications
including data science and machine learning. The authors stated
that the usage of opensource technologies is expanding and
listed several tools used in DevOps research, including Jenkins,
Docker, and Kubernetes.The report also addresses the
difficulties encountered in DevOps research, including the need
for stronger security measures and a more integrated approach
to DevOps. The absence of DevOps practice standardization
and the need for further empirical research were also mentioned
by the authors as topics that need more focus.Overall, the article
offers a thorough analysis of the present status of DevOps
research and identifies a number of promising topics for further
study. Researchers, practitioners, and decision-makers who are
interested in learning about the most recent DevOps trends,
technologies, and difficulties may find the results to be helpful.
T. Golis et al. [2] The work offers a case study of a real-
world system where service configuration management was
automated using Ansible, and the authors emphasize the
advantages of doing so.The relevance of service configuration
management in cloud computing, which entails setting multiple
services including web servers, databases, and load balancers,
is covered in the first section of the article.
A. Petricko et al. [3] The work gives a general review of the
idea of IaC, identifies its advantages and difficulties, and
examines present trends and IaC's foreseeable future.IaC is
introduced in the article as the process of controlling and
providing infrastructure using code rather than through manual
procedures. The authors point out that greater agility,
repeatability, and consistency are just a few advantages that IaC
may provide. The authors do point out that IaC may be difficult,
however, since it requires learning new skills and runs the risk of
making mistakes.The authors then go on to detail how they
conducted a systematic evaluation of the literature, which
includes looking for relevant studies using a variety of databases
and criteria. Future directions in IaC include the use of machine
learning and artificial intelligence to automate IaC operations.
IaC is still a young discipline, according to the scientists, and
there is still much to learn about its effects and ideal procedures.
F. Alkhabbas et al. [4] The authors' DevOps automation
framework was developed through sporadic rearranging and
removal of text. Its uniqueness is apparent due to the intentional
avoidance of the most logical phrasing. administration and
deployment automated through development Described next are
a variety of uses in multi-cloud environments. The automation
layer, the infrastructure layer, as seen by the authors.The trilevel
structure consists of the physical layer, data link layer, and the
application layer. Infrastructure that underpins the frame. Cloud
service providers are included in the multi-cloud system
Provided by the infrastructure, networking and multi-cloud
architecture involves layering infrastructure.
J. DesLauriers et al. [5] The author describe the Methods of a
non-automated nature are highlighted by the writers. and are
prone to mistakes, deployment can take a long time. The authors
contend that automation is an attractive option, which is why it
should be pursued. To automate their process, they detailed their
use of Ansible. Using Ansible playbooks, Docker containers can
be deployed with ease. Deployments are performed using
Ansible after a sequence of actions. The target servers are defined
using containers, which are used to send data sporadically. The
dependencies and Docker container images—they go together
like two peas in a pod. Ansible, according to writers, provides a
straightforward and speedy option. Deploying has never been
easier with an automated solution that lowers the burden of
manual intervention. Risk and effectiveness get tangled when
mistakes happen. There was a startling example where a case was
used to show the point. Their strategy is reviewed in the study by
the writers.For the deployment of, their method was used and
here's how it was done.
 Reference Main Topic Tools/Technologies Research Main Findings
Methodology
[1] Research problems, tools, Jenkins, Docker, Kubernetes, A thorough analysis of 294 Microservices, automation,
and trends in DevOps Ansible, etc. peer-reviewed articles and containerization are all
being used more and more.
[2] Automated management of Ansible Case study using a genuine Service configuration
service configuration system management may be made
easier with Ansible, and
manual configuration can
take less time and effort.
Terraform, Ansible, Chef, Systematic literature Infrastructure may become
[3] Infrastructure as code: trends, Puppet, etc. more agile, dependable, and
issues, and directions for the scalable by using
future infrastructure as code.
[4] Framework for DevOps Ansible, AWS, Azure, etc. The framework that is Ansible may be used in the
automation in a multi-cloud suggested and a case study proposed framework to
context using a real-world system automate the deployment,
setup, and monitoring of
multi-cloud systems.
[5] Docker container deployment Ansible, Docker Case study using a genuine Ansible can automate Docker
automation in DevOps system container deployment, saving
time and effort over manual
deployment.
Table 1. Basic Comparison of Related Work

III. METHODOLOGY B. Automation Utilizing mathematical formulas or algorithms

presents an opportunity to automate infrastructure resource
Employing previous techniques, manual deployment and
deployment and provisioning through automation and
administration of infrastructure involved plenty of mistakes and
orchestration. The process can establish the preferred
consumed much energy. Establishing networks, servers, and configuration, minimizing the need for manual
other resources within these processes extensively required
intervention. This approach fosters prompt and precise
diligent repetition. This manual protocol was not only a time-
allocation of resources, which reduces the possibility of
consuming process, but its inconsistency also caused variations
setbacks and errors that would result from manual handling.
in settings and setups. Developers were also facing difficulty
C. Optimization: Infrastructure models can benefit from the
coping with the infrastructure's obscurity and limitations of
application of mathematical optimization techniques to
manipulation. The IT team was responsible for the resource identify the most cost-efficient and efficient configurations.
provisions; thus, deployments were mainly put off and the
By utilizing algorithms, tasks like optimizing resource
infrastructure lacked adaptability. Introducing a mathematical
allocation, load balancing, and scaling strategies can be
modeling approach, the proposed methodology seeks to remedy
easily achieved, ultimately leading to optimal performance,
the challenges and deficiencies that arise in manually deploying
reliability, and cost-efficiency of the infrastructure.
and administering infrastructure. However, cooperation among D. Mathematical models enable the reproduction of
multiple teams was required to modify the infrastructure, which
infrastructure setups in various sites, thus promoting
complicated matters and exacerbated the possibility of setbacks
replication and scalability. Easily replicating identical
and errors [7].
configurations for testing, development, or deployment in
The mathematical modeling of the proposed methodology multiple locations becomes possible with mathematical
involves the following key aspects: representations capturing the settings.
E. Real-time visibility and control over infrastructure can be
A. Infrastructure Configuration: To minimize errors and ensure
achieved with the integration of monitoring systems and
consistency, it is possible to employ mathematical models to
mathematical models. By updating the models with current
define and specify the infrastructure configuration, including
performance data, anomalies can be detected and automated
network setup, server configurations, resource allocation, and
corrective actions taken, providing proactive monitoring.
other related parameters. With these models, the dependencies
The result is an enhanced stability, reliability, and security
and relationships between components can be captured,
of the infrastructure.
making them more efficient.
IaC, or infrastructure as code, has come to be seen as a solution to
many of these issues. IaC is a methodology for more automated,
programmatically controlling infrastructure. Developers can use
code to design and provision infrastructure resources rather than
manually configuring hardware and software resources.
Developers can benefit from the same tools, procedures, and best
practices used in software development by treating infrastructure
like code. This comprises continuous integration and deployment
(CI/CD) pipelines, automated testing, and version control. This
leads to improved cooperation between the development and
operations teams as well as more effective and dependable
infrastructure management. Effectively implementing IaC still
presents some difficulties
Fig:2 Comparison between Manual Deployment & Iaac Tool
As Shown this Fig 2 the line chart compares the scores for
different categories (reproducibility, consistency, and speed)
between manual deployment and IaC tools. The x-axis represents
the categories, while the y-axis represents the score in percentage.
The scores for manual deployment are shown with a blue line,
and the scores for IaC tools are shown with a red line. Each data
point is marked with a circular marker. the manual deployment is
much time consuming. By comparing the position and trend of
the lines, you can observe the relative performance of manual
deployment versus IaC tools across the categories. If the red line
is consistently higher than the blue line, it indicates that IaC tools
have higher scores in those categories. On the other hand, if the
blue line is consistently higher, it suggests that manual
deployment fares better in those areas.
IV. ANALYSIS OF IAAC TOOL
Terraform: Takes the declarative method. It speaks its own
language, known as Hashicorp Configuration Language (HCL),
which is widely regarded as being very simple to learn and highly
readable by humans. On Go, HCL is based. Terraform's provider
mechanism, which has thousands of accessible options, may be
used with virtually any cloud provider as well as on-premise
infrastructure. This is why Terraform is so popular; it is a logical
choice if you want to configure infrastructure across various
cloud platforms and architecture using the same language and
style. Even if you only want to utilize it for one cloud platform,
in my opinion (e.g., Microsoft Azure). Terraform can query,
construct, maintain, and alter the infrastructure as specified in
your configuration files thanks to the state file, which specifies
the current state of the infrastructure [8]. As Shown in Fig 3
Dependency mapping between resources is carried out
automatically in the background by Terraform and is generally
concealed from the user, but it can be managed if necessary. The
order in which resources are created is referred to as dependency
mapping. Take the creation of a virtual machine as an example; in
order for it to be successful, you must first have a VNET, subnet,
disc, and key vault for disc encryption in place.Terraform ensures
resources are created in the correct order. The depends on met-
argument can be used in the configuration to accomplish this if
these need to be manually changed.
Fig: 3. Work Flow of Terraform
CloudFormation: For the creation and management of AWS
resources, Amazon Web Services (AWS) offers AWS
CloudFormation. It enables you to express your infrastructure as
code in a template that can be used to predictably and repeatedly
add, update, or remove resources. To define a stack, which is a
group of AWS resources that are produced and maintained as a
single entity, you can use CloudFormation to construct templates
in either JSON or YAML format. Managing modifications to your
stack over time and, if necessary, rolling back to a previous version
are both possible using CloudFormation. Both small and large
businesses use CloudFormation, a potent tool for managing
infrastructure on AWS To use it effectively, it does need some
familiarity with CloudFormation templates and AWS. You can
construct and provision AWS infrastructure deployments
predictably and repeatedly with AWS CloudFormation. Without
having to worry about building and configuring the underlying
AWS infrastructure, it enables you to use AWS products like
Amazon EC2, Amazon Elastic Block Store, Amazon SNS, Elastic
Load Balancing, and Auto Scaling to build highly dependable,
highly scalable, cost-effective applications in the cloud.
Ansible: DevOps experts frequently utilize Ansible, an
opensource, cross-platform resource provisioning automation
tool, to implement an "infrastructure as code" strategy for
continuous software delivery. The Ansible automation platform
has developed over time to provide advanced automation
solutions for administrators, operators, and IT decision-makers
 across multiple technical disciplines. It is the unofficial
standard for IT automated systems and a leading enterprise
automation solution with thriving open-source software [9]. It
can manage Microsoft and Unix architectures and works on a
variety of Unix-like platforms. It includes text that is illustrative
of system settings. Ansible was developed by Michael DeHaan
and was bought by Red Hat in 2015. As Shown in Fig 4 Ansible
is a system without an agent that can run commands remotely
using SSH or Windows Remote Management connections
(enabling remote PowerShell execution). Ansible is an open-
source IT automation engine that can increase the scalability,
consistency, and dependability of your IT infrastructure while
potentially saving you time at work.
Fig: 5. Speed of Deployment of Iaac Tools
Presented in Figure 8, one can utilize a line chart to observe
the deployment times for various IaC tools and compare their
speeds. The x-axis signifies the tools being examined,
whereas the y-axis represents the deployment duration in
minutes. This chart permits a quick and effective comparison
of the pace and effectiveness of the deployment process for
each tool. Such data is crucial in choosing the best tool for
specific infrastructure provisioning necessities.
2. Standardization and Consistency: IaC promotes
standardization and consistency across infrastructure
deployments. Infrastructure configurations can be version-
controlled and reused, ensuring that all environments are set
up in the same way. This reduces configuration drift and
minimizes inconsistencies that may cause issues.

Fig: 4. Work Flow of Ansible

VI. RESULT AND DISSCUSION

Efficiency, performance, and reliability of infrastructure deployment
and maintenance processes are being improved by this approach. Our
results and findings concerning these three aspects of Infrastructure
as Code are being presented here.
Efficiency:
Efficiency refers to the ability of IaC to streamline infrastructure
deployment and management processes, reduce human error, and
optimize resource utilization. The results indicate that IaC has
several efficiency benefits:
1. Deployment Speed: IaC boasts a plethora of efficiency benefits. It
optimizes resource utilization, streamlines infrastructure
deployment and management processes, and reduces human error.
Through these findings, it is evident that IaC aligns with the
pursuit of efficiency.
Fig: 6. Standardization and Consistency of Iaac Tools
As Shown in Fig 9,the X-axis represents the Iaac tools,and
the Y-axis represents the score.The chart includes labels for
the axis and a title.The legend differentiates the lines for
standardization and consistency scores while consistency
emphasizes maintaining the desired state of the
infrastructure over time.Both aspects are essentials for
achieving efficient and reliable infrastructure .
3. Scalability: IaC provides scalability by allowing easy
replication and scaling of infrastructure resources. With IaC
tools, such as Terraform or CloudFormation, infrastructure can
be easily replicated or expanded based on demand, ensuring
efficient resource utilization.
 state quickly and reliably in the event of failures.

3. Monitoring and Alerting: IaC tools often integrate with

monitoring and alerting systems. This enables proactive
monitoring of the infrastructure, automatic alerting of potential
issues, and the ability to take corrective actions promptly. These
capabilities enhance the reliability of the infrastructure.

As Shown Fig 11 the line chart compares the reproducibility scores

of different IaC tools (Terraform, Ansible, CloudFormation, and Pulumi)
represented on the x-axis, and the reproducibility scores (in
percentage) represented on the y-axis. Each data point is marked with
a circular marker, and a solid blue line connects the data points.

Fig: 7. Scalability of Iaac Tools

As Shown in Fig 10 When visualizing the scalability of IaC tools using
a line chart, each tool is typically represented on the x-axis, while
the scalability rating or metric is plotted on the y-axis. The chart
can help compare and identify the relative scalability of different tools,
allowing for informed decision-making when selecting an
appropriate IaC solution for a specific project or organization. By
analysing and comparing the scalability of IaC tools, organizations
can choose the most suitable tool that aligns with their infrastructure
requirements, growth potential, and performance expectations

a) Performance:
Performance relates to the responsiveness and efficiency of the Fig: 8. Infrastructure Reproductibility of Iaac Tools
infrastructure under different workloads. The findings suggest
that IaC positively impacts performance in the following ways:
VIII. CONCLUSION
1. Infrastructure Optimization: With IaC, infrastructure can be
In conclusion, Infrastructure as Code (IaC) has emerged as a
designed and optimized based on best practices and
crucial method for businesses trying to optimize their processes and
performance requirements. It allows for fine-tuning of
boost productivity in a DevOps setting. IaC allows resources to be
infrastructure configurations to achieve optimal performance,
deployed consistently and removes the possibility of human mistakes
such as load balancing, auto-scaling, and efficient resource
by specifying and delivering infrastructure using a descriptive
allocation.
model. Additionally, IaC streamlines auditing and tracing
procedures, making compliance simpler to achieve. Additionally,
2. Automated Testing: IaC supports automated testing of
IaC frees up time and resources for organizations by allowing
infrastructure deployments. This ensures that performance-
developers and testers to create and run scripts in test
related aspects, such as response times, throughput, and
environments. The empirical research in the prior study showed that
latency, can be measured and validated. Automated testing
IaC tools like Terraform may assist organizations in many ways,
enables early identification and resolution of performance
including scalability, maintainability, and cooperation. Eventhough
issues.
there are still certain difficulties with IaC, such as complicated
syntax and error handling, further study may help solve these problems
b) Reliability: and improve IaC's effectiveness in DevOps situations. IaC is a crucial
Reliability refers to the stability and availability of the strategy for businesses that want to maintain their competitive edge
infrastructure. IaC contributes to reliability in the following and react rapidly to changing market conditions.
aspects:

1. Infrastructure Reproducibility: With IaC, infrastructure can be

easily reproduced and re-created in a consistentmanner. This
ensures that the infrastructure can be quickly rebuilt in case
failures.
2. Disaster Recovery: IaC enables the definition of disaster
recovery procedures as part of the infrastructure
configuration. By automating the recovery process, IaC
ensures that the infrastructure can be restored to a functional
 IX. REFRENCE
[1] A. Dalvi, "Cloud Infrastructure Self Service Delivery System
using Infrastructure as Code," 2022 International Conference on
Computing, Communication, and Intelligent Systems (ICCCIS),
Greater Noida, India, 2022, pp. 1-6.
[2] T. Golis, P. Dakić and V. Vranić, "Creating Microservices and
using infrastructure as code within the CI/CD for dynamic
container creation," 2022 IEEE 16th International Scientific
Conference on Informatics (Informatics), Poprad, Slovakia, 2022,
pp. 114-119.
[3] A. Petricko, P. Dakic and V. Vranic, "Comparison of visual
occupancy detection approaches for parking lots and dedicated
containerized REST-API server application", Proceedings of the
Ninth Workshop on Software Quality Analysis Monitoring
Improvement and Applications, vol. 3237, September 11-14,
2022.
[4] F. Alkhabbas, R. Spalazzese, M. Cerioli, M. Leotta and G.
Reggio, "On the Deployment of IoT Systems: An Industrial
Survey", 2020 IEEE International Conference on Software
Architecture Companion (ICSA-C), pp. 17-24, 2020.
[5] J. DesLauriers, J. Kovacs and T. Kiss, "Abstractions of
Abstractions: Metadata to Infrastructure-as-Code," 2022 IEEE
19th International Conference on Software Architecture
Companion (ICSA-C), Honolulu, HI, USA, 2022, pp. 230-232.
[6] A. A. S. Sabil, H. Y. Martono and D. I. Permatasari, "Effective
Building Data Warehouse Infrastructure by Code in Cloud
Platform," 2022 International Electronics Symposium (IES),
Surabaya, Indonesia, 2022, pp. 418-424.
[7] D. R. Bharadwaj, A. Bhattacharya and M. Chakkaravarthy,
"Cloud Threat Defense — A Threat Protection and Security
Compliance Solution", 2018 IEEE International Conference on
Cloud Computing in Emerging Markets (CCEM), pp. 95-99,
2018.
[8] R. Rompicharla and B. R. P. V, "Continuous Compliance
model for Hybrid Multi-Cloud through Self-Service
Orchestrator", 2020 International Conference on Smart
Technologies in Computing Electrical and Electronics
(ICSTCEE), pp. 589-593, 2020.
[9] V. Barannik, "Technology of Structural-Binomial Coding to
Increase the Efficiency of the Functioning of Computer Systems,"
2022 IEEE 4th International Conference on Advanced Trends in
Information Theory (ATIT), Kyiv, Ukraine, 2022, pp. 96-100, doi:
10.1109/ATIT58178.2022.10024205.
[10] M. M. Ibrahim, S. M. Syed-Mohamad and M. H. Husin,
"Managing quality assurance challenges of devops through
analytics", Proceedings of the 2019 8th International Conference
on Software and Computer Applications, 2019.
[11] M. Krocka, P. Dakic and V. Vranic, "Extending parking
occupancy detection model for night lighting and snowy
weather conditions", 2022 IEEE Zooming Innovation
Consumer Technologies Conference (ZINC), pp. 203-208,
2022.
[12] Vladimir Barannik, Valeriy Barannik, D. Havrylov and A.
Sorokun, "Development Second and Third Phase of the
Selective Frame Processing Method", 3rd International
conference on Advanced Information and Communications
Technologies (AICT), pp. 54-57, 2019.
[13] G. Pierantoni, T. Kiss, G. Terstyanszky, J. DesLauriers, G.
Gesmier and H.-V. Dang, "Describing and processing topology
and quality of service parameters of applications in the cloud",
Journal of Grid Computing, pp. 1-18, 2020.
[14] M. Shahin M. Ali Babar and L. Zhu "Continuous
integration delivery and deployment: A systematic review on
approaches tools challenges and practices" IEEE access vol. 5
pp. 3909-3943 2017.
[15] A. Malviya and R. K. Dwivedi, "A comparative analysis
of container orchestration tools in cloud computing", 2022 9th
International Conference on Computing for Sustainable Global
Development (INDI-ACom), pp. 698-703, 2022.
[16] H. Teppan, L. H. Flå and M. G. Jaatun, "A Survey on
Infrastructure-as-Code Solutions for Cloud Development,"
2022 IEEE International Conference on Cloud Computing
Technology and Science (CloudCom), Bangkok, Thailand,
2022, pp. 60-65.
[17] N. Petrović, M. Cankar and A. Luzar, "Automated
Approach to IaC Code Inspection Using Python-Based
DevSecOps Tool," 2022 30th Telecommunications Forum
(TELFOR), Belgrade, Serbia, 2022, pp. 1-4.
[18] J. Alonso, C. Joubert, L. Orue-Echevarria, M. Pradella and
D. Vladusic, "Programming trustworthy Infrastructure As Code
in a Secure Framework", First SWForum workshop on
trustworthy software and open source (SWForum.eu). CEUR-
WS.org, vol. 2878, pp. 16-23, 2021.
[19] M. Y. Bagus, F. Arbi, R. Elisa and I. Hermawan, "Wireless
Infrastructure uses DSSS (Direct Sequence Spread Spectrum)
Mechanism for Smart Government Concept," 2022 5th
International Conference of Computer and Informatics
Engineering (IC2IE), Jakarta, Indonesia, 2022, pp. 198-203.
[20] A. Bijwe and P. Shankar, "Challenges of Adopting DevOps
Culture on the Internet of Things Applications - A Solution
Model," 2022 2nd International Conference on Technological
Advancements in Computational Sciences (ICTACS),
Tashkent, Uzbekistan, 2022, pp. 638-645.
M. A. Lopez-Pena, J. Diaz, J. E. Perez and H. Humanes,
"DevOps for IOT systems: Fast and continuous monitoring
feedback of system availability", IEEE Internet of Things