Automated Infrastructure Creation from Application Code Data Structures

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing process of creating infrastructure for cloud-based services involves duplication and inconsistency between infrastructure as code (IaC) and application code, leading to inefficiencies and potential incompatibilities that can render applications inoperable.

Innovation Solution

An automated infrastructure creation service that processes application code to identify data structures, generates manifests based on these structures, and uses IaC to create infrastructure for a virtual computing environment, thereby eliminating duplication and ensuring consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If infrastructure is created using traditional IaC with separate code descriptions, then infrastructure can be programmatically created, but duplication and inconsistency occur between IaC and application code

Engineering Contradiction:

Improveinfrastructure creation efficiencyVSAvoidconsistency between IaC and application code

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent merges the infrastructure definition and application code into a single unified codebase. The infrastructure is defined as data structures within the application code itself, eliminating the need for separate IaC files. This integration ensures that the infrastructure description and application logic are always consistent, as they reside in the same code repository and are versioned together.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent uses serialization to create a copy of the infrastructure definition from the application code. The data structures in the application code are serialized into a manifest format that can be consumed by infrastructure creation tools. This copying mechanism ensures that the infrastructure definition can be extracted and processed without duplicating the entire application code, maintaining consistency while enabling automated infrastructure creation.

Inventive Principle:

Principle #26Copying

2Adaptability or versatility

If separate descriptions of computing resources are provided in both IaC and application code, then infrastructure can be created and applications can utilize resources, but errors and incompatibilities arise

Engineering Contradiction:

Improveflexibility in resource descriptionVSAvoidaccuracy of resource configuration

Core Design Contradiction:

Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent inverts the traditional approach by having the application code define the infrastructure rather than having separate IaC files define it. Instead of writing infrastructure code that the application then uses, the application's data structures directly specify the infrastructure requirements. This inversion eliminates the possibility of mismatches between infrastructure definitions and application expectations, as the application itself is the source of truth.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The application code performs self-description of its infrastructure requirements through its data structures. The application automatically generates the infrastructure manifest from its own code, eliminating the need for manual IaC configuration. This self-service approach ensures that the infrastructure definition is always accurate and consistent with the application's actual needs, as it is generated directly from the application's source code.

Inventive Principle:

Principle #25Self-service

3Reliability

If manual synchronization of infrastructure definitions is attempted, then consistency can be maintained, but time and resources are wasted

Engineering Contradiction:

Improveconsistency maintenanceVSAvoidtime for synchronization

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by serializing the infrastructure definition from the application code before the infrastructure creation process begins. The manifest is generated as part of the build or deployment process, ensuring that the infrastructure definition is ready and consistent before resources are allocated. This preliminary serialization eliminates the need for ongoing manual synchronization, as the infrastructure definition is automatically prepared in advance from the application code.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12307278B1Infrastructure creation based on application code

Publication Date: 2025.05.20 AMAZON TECH INC

AI summary

An automated infrastructure creation service of a service provider network may be used to create infrastructure for a virtual computing environment of the service provider network based on application code. The service identifies a data structure(s) in application code, the application code to be executed in a virtual computing environment of the service provider network, and the service generates a manifest(s) based on the data structure(s) identified in the application code. Infrastructure as code (IaC) can then be executed to create infrastructure for the virtual computing environment based at least in part on the manifest(s). Accordingly, the IaC uses the application code to create infrastructure. In this way, duplicity in the process of developing IaC and application code is reduced, or eliminated, and errors in the respective code bases are mitigated.