
Infrastructure as Code with Terraform: A Comparative Study of Manual and Automated Infrastructure Provisioning on Amazon Web Services | IJCT Volume 13 – Issue 6 | IJCT-V13I6P98
IJCT
International Journal of Computer Techniques
ISSN 2394-2231 · Peer-Reviewed · Open Access
📚 Volume 13, Issue 6
📅 November 18, 2026
📄 Pages 824–830
🔖 ID: IJCT-V13I6P98
Table of Contents
ToggleInfrastructure as Code with Terraform: A Comparative Study of Manual and Automated Infrastructure Provisioning on Amazon Web Services
Author(s)
Omkar Balaso Pawar, Aniket Ganesh Honrao, Azad Bashir Shaikh, Pavan Dnyanoba Magar
Abstract
Infrastructure as Code (IaC) describes cloud resources in files that can be reviewed, versioned, and reused. Terraform is a widely used IaC tool that can create Amazon Web Services (AWS) resources from declarative configuration. This paper presents a framework for comparing manual provisioning through the AWS console with provisioning using Terraform. The framework looks at provisioning time, hands-on effort, configuration errors, correctness, repeatability, and maintainability. The proposed experiment builds the same AWS environment with both approaches, using repeated trials and one common validation checklist. To show how the analysis and formatting would work, the results section uses a clearly labelled hypothetical dataset of five trials per approach. In this dataset, the manual process averages 33.8 minutes and the Terraform apply stage averages 12.0 minutes, a difference of 64.5% for that stage. This is not a fair end-to-end comparison, because the Terraform figure leaves out the time spent writing the configuration. The values are examples only and are not real observations. The paper concludes that a valid comparison must measure both initial setup and repeated deployment, use equivalent infrastructure, report errors honestly, and consider security and cloud cost.
Keywords
Infrastructure as Code, Terraform, AWS, cloud computing, DevOps, provisioning, automation, repeatability
Conclusion
This study offers a way to compare manual AWS provisioning with Terraform-based Infrastructure as Code. It draws on established literature and a practical method that looks at timing, effort, errors, correctness, and repeatability for both approaches, together with security. The hypothetical results show how measurements might be presented, but they do not show real-world performance. A final research conclusion must come from trials in which both methods create the same resources and the timing boundaries of each method are reported openly. Future work might compare Terraform with AWS CloudFormation [11], include more trials, test more architectures, and add automated security checks.
References
[1] A. Rahman, R. Mahdavi-Hezaveh, and L. A. Williams, “A systematic mapping study of infrastructure as code research,” Information and Software Technology, vol. 108, pp. 65–77, 2019, doi: 10.1016/j.infsof.2018.12.004.
[2] K. Morris, Infrastructure as Code: Managing Servers in the Cloud, 2nd ed. Sebastopol, CA, USA: O’Reilly Media, 2021.
[3] T. Sharma, M. Fragkoulis, and D. Spinellis, “Does your configuration code smell?,” in Proc. 13th Working Conf. Mining Software Repositories (MSR), 2016, pp. 189–200, doi: 10.1145/2901739.2901761.
[4] J. Schwarz, A. Steffens, and H. Lichter, “Code smells in infrastructure as code,” in Proc. 12th Int. Conf. Quality of Information and Communications Technology (QUATIC), 2018, doi: 10.1109/QUATIC.2018.00040.
[5] A. Rahman, C. Parnin, and L. Williams, “The seven sins: Security smells in infrastructure as code scripts,” in Proc. IEEE/ACM 41st Int. Conf. Software Engineering (ICSE), 2019, doi: 10.1109/ICSE.2019.00083.
[6] HashiCorp, “Terraform documentation.” [Online]. Available: https://developer.hashicorp.com/terraform/docs (accessed Oct. 12, 2026).
[7] Amazon Web Services, “AWS documentation.” [Online]. Available: https://docs.aws.amazon.com/ (accessed Oct. 12, 2026).
[8] P. Mell and T. Grance, The NIST Definition of Cloud Computing, NIST Special Publication 800-145, 2011, doi: 10.6028/NIST.SP.800-145.
[9] D. Regvart, I. Vlahović, and M. Balković, “A controlled comparative evaluation of infrastructure as code tools: Deployment performance and maintainability across Terraform, Pulumi, and AWS CloudFormation,” Applied Sciences, vol. 16, no. 6, Art. no. 2971, 2026, doi: 10.3390/app16062971.
[10] [Authors to be confirmed], “Comparative study of Terraform-based Infrastructure-as-Code and manual AWS console provisioning,” SCITEPRESS, 2026. [Online]. Available: https://www.scitepress.org/publishedPapers/2026/148730/pdf/index.html
[11] Amazon Web Services, “AWS CloudFormation User Guide.” [Online]. Available: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html (accessed Oct. 12, 2026).
[12] J. Humble and D. Farley, Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation. Boston, MA, USA: Addison-Wesley, 2010.
[2] K. Morris, Infrastructure as Code: Managing Servers in the Cloud, 2nd ed. Sebastopol, CA, USA: O’Reilly Media, 2021.
[3] T. Sharma, M. Fragkoulis, and D. Spinellis, “Does your configuration code smell?,” in Proc. 13th Working Conf. Mining Software Repositories (MSR), 2016, pp. 189–200, doi: 10.1145/2901739.2901761.
[4] J. Schwarz, A. Steffens, and H. Lichter, “Code smells in infrastructure as code,” in Proc. 12th Int. Conf. Quality of Information and Communications Technology (QUATIC), 2018, doi: 10.1109/QUATIC.2018.00040.
[5] A. Rahman, C. Parnin, and L. Williams, “The seven sins: Security smells in infrastructure as code scripts,” in Proc. IEEE/ACM 41st Int. Conf. Software Engineering (ICSE), 2019, doi: 10.1109/ICSE.2019.00083.
[6] HashiCorp, “Terraform documentation.” [Online]. Available: https://developer.hashicorp.com/terraform/docs (accessed Oct. 12, 2026).
[7] Amazon Web Services, “AWS documentation.” [Online]. Available: https://docs.aws.amazon.com/ (accessed Oct. 12, 2026).
[8] P. Mell and T. Grance, The NIST Definition of Cloud Computing, NIST Special Publication 800-145, 2011, doi: 10.6028/NIST.SP.800-145.
[9] D. Regvart, I. Vlahović, and M. Balković, “A controlled comparative evaluation of infrastructure as code tools: Deployment performance and maintainability across Terraform, Pulumi, and AWS CloudFormation,” Applied Sciences, vol. 16, no. 6, Art. no. 2971, 2026, doi: 10.3390/app16062971.
[10] [Authors to be confirmed], “Comparative study of Terraform-based Infrastructure-as-Code and manual AWS console provisioning,” SCITEPRESS, 2026. [Online]. Available: https://www.scitepress.org/publishedPapers/2026/148730/pdf/index.html
[11] Amazon Web Services, “AWS CloudFormation User Guide.” [Online]. Available: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html (accessed Oct. 12, 2026).
[12] J. Humble and D. Farley, Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation. Boston, MA, USA: Addison-Wesley, 2010.
📋 How to Cite This Paper
Omkar Balaso Pawar, Aniket Ganesh Honrao, Azad Bashir Shaikh, Pavan Dnyanoba Magar (2026). Infrastructure as Code with Terraform: A Comparative Study of Manual and Automated Infrastructure Provisioning on Amazon Web Services. International Journal of Computer Techniques, 13(6), 824–830. ISSN: 2394-2231. DOI: https://doi.org/10.5281/zenodo.24348555








