Federated Infrastructure Seeding Engine for Governance and Scalability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing Infrastructure as Code (IaC) solutions do not effectively address internal governance needs of organizations, such as controlling who can deploy features, access them, and managing hardware infrastructure inventory, especially when scaling to large organizations with varying hardware types and application patterns.

Innovation Solution

The deployment of federated infrastructure as code involves an infrastructure seeding engine that receives and publishes extensible application patterns, generates metadata and configurations, creates execution isolations, applies security policies, and links source code to continuous integration/continuous development pipelines, achieving an immutable infrastructure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If commercial IaC products are used, then deployment automation is achieved, but internal governance needs are not addressed

Engineering Contradiction:

Improvedeployment automationVSAvoidgovernance control

Core Design Contradiction:

Extent of automationVSReliability

Solution Approach 1:

The patent introduces a governance layer as an intermediary between the IaC deployment system and organizational policies. This governance layer includes policy definition modules, approval workflows, and compliance checking mechanisms that mediate between automated deployment requests and organizational governance requirements, enabling both automation and control to coexist

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If IaC is implemented without federation, then deployment speed improves, but scalability to large organizations deteriorates

Engineering Contradiction:

Improvedeployment speedVSAvoidscalability

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the IaC system into federated units that can operate independently at different organizational levels. Each federated unit can deploy infrastructure autonomously while adhering to governance policies, allowing the system to scale across large organizations without sacrificing deployment speed. The segmentation enables parallel deployments across multiple teams and regions

Inventive Principle:

Principle #1Segmentation

3Device complexity

If hardware variations are not accounted for, then system simplicity is maintained, but adaptability to different hardware types deteriorates

Engineering Contradiction:

Improvesystem simplicityVSAvoidhardware adaptability

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent uses parameter-based configuration to handle hardware variations. Instead of creating complex specialized systems for each hardware type, the IaC templates accept hardware-specific parameters as inputs. This allows the same deployment framework to adapt to different hardware configurations by simply changing parameters, maintaining system simplicity while achieving hardware diversity support

Inventive Principle:

Principle #35Parameter changes

4Ease of operation

If access controls are not implemented, then ease of deployment is improved, but security deteriorates

Engineering Contradiction:

Improvedeployment easeVSAvoidsecurity risk

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent implements preliminary access control checks and approval workflows before deployments are executed. Security policies, role-based access controls, and mandatory approval steps are configured in advance and automatically enforced during the deployment process. This preliminary action ensures security requirements are met before deployment begins, maintaining both ease of operation and security

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12321736B2Systems and methods for deploying federated infrastructure as code

Publication Date: 2025.06.03 JPMORGAN CHASE BANK NA

AI summary

A method for deploying federated infrastructure as code may include an infrastructure seeding engine: receiving a plurality of extensible application patterns; publishing the extensible application patterns to an application pattern catalog; receiving an instantiate request comprising a selection of one of the plurality of extensible application patterns and a blueprint, wherein the blueprint identifies a deployment technology; generating metadata for the selected extensible application pattern; generating a configuration for the selected extensible application pattern; creating execution isolations for deployments based on the metadata; applying security policies to the selected extensible application pattern; generating source code for the selected extensible application pattern; creating and linking the source code for the selected extensible application pattern to a continuous integration/continuous development pipelines; initializing the source code to an infrastructure; and deploying an application artifacts infrastructure, wherein the deployment achieves an immutable infrastructure.