> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/extras-overview/video-transcripts/duplocloud-uses-infrastructure-as-code-to-stitch-together-devops-lifecycle.md). # DuploCloud Uses Infrastructure-as-Code to Stitch Together DevOps Lifecycle View the whole [DuploCloud Uses Infrastructure-as-Code to Stitch Together DevOps Lifecycle](https://duplocloud.com/videos/#gallery-6) video. ## Transcript **NARRATOR:** Building and operating infrastructure in the public cloud is challenging. It revolves around the five pillars of operational excellence, security, reliability, performance, and cost optimization. This is a broad taxonomy of thought operations. It starts from building a network infrastructure that includes VPCs and hybrid connectivity. Next comes application infrastructure. This involves virtual machines, data stores, along with the right security policies and backup configuration. On top of the app infra is app provisioning where we see Kubernetes, serverless, and spark clusters. There's logging and monitoring. CI/CD makes this a repeatable process. Compliance controls are needed across the board. Today, certified cloud experts automate these functions by manually writing code that spans thousands of lines. We see cargo culting, with every engineer, bringing their own style, favorite programming language, and tools. With expanding infrastructure, the size of the codebase and team grows. The bigger the system, the harder to make changes, decreasing productivity. One has to understand what code to change. Once updated, peers need to do code review, then tests are to be performed, followed by a roll out. A simple user request to open a port for an application requires subject matter experts and still takes days. Lack of cloud subject matter experts is the single biggest blocker to cloud adoption. Hiring a DevOps workforce is hard and expensive. Today, on average, to build and operate a 50-VM cloud infrastructure, companies require two DevSecOps engineers. But did you know that inside Amazon and Microsoft, they manage millions of virtual machines with only 1000-odd people? To understand how, imagine for a moment being assisted by a DevOps bot, which had the ability to auto-generate this infrastructure configuration based on a rules engine that combines user requirements, subject matter expertise, and principles of a well-architected framework. Cloud operations might very well involve thousands of configurations that overwhelm humans, but in the age of AI, bots can auto-generate these. At DuploCloud, we have built such a robot. The bot installs in a virtual machine in your cloud account. Users can easily interface it with it through a browser or API. There, they configure their application needs in simple declarative terms and the bot auto-generates the underlying infrastructure policies. Whether doing a first-time deployment or ongoing operations, it manages a complete application and infrastructure life cycle. Today, the bots are operational in over 25 enterprises, managing over 3000 virtual machines, and 250 applications. Users do 5000 self-service deployments a week. For a product demo, go to duplocloud.com/demo. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.duplocloud.com/docs/automation-platform/extras-overview/video-transcripts/duplocloud-uses-infrastructure-as-code-to-stitch-together-devops-lifecycle.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.