Cloud Deployment Package Inversion for Secure Environment Setup

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Enterprises face challenges in efficiently managing and deploying server environments within cloud computing platforms, as they need to maintain software and data while adhering to strict security policies that restrict external access, limiting the ability to push deployment from external systems.

Innovation Solution

A software system provides a deployment package with tools and automation scripts that customers can use within their cloud computing accounts to create and manage server environments, including container-based infrastructure, without requiring external interaction, thus enabling secure and efficient deployment and management of multiple environments on-demand.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If deployment tools are provided externally to push deployment to customer accounts, then deployment capability is provided, but security policies are violated due to external access requirements

Engineering Contradiction:

Improvedeployment capabilityVSAvoidsecurity policy violation

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

Instead of pushing deployment from external systems to customer accounts (external→internal), the system inverts the approach by having deployment tools run within the customer's own account (internal→internal). The customer's account becomes the deployment origin, eliminating external access requirements while maintaining full deployment functionality.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The patent introduces an intermediary mechanism where a software provider's account hosts deployment tools that can be invoked by customers. This intermediary account acts as a secure bridge, allowing deployment functionality without direct external access to customer accounts, thus satisfying security policies while providing deployment capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If deployment tools run within customer accounts, then security is improved, but deployment infrastructure complexity increases

Engineering Contradiction:

ImprovesecurityVSAvoiddeployment infrastructure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal deployment infrastructure that can serve multiple customers through the software provider's account. This multi-functional system provides deployment capabilities to numerous customers without each customer needing separate infrastructure, thus reducing overall complexity while maintaining security through local execution.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Customers invoke deployment tools using their own credentials and within their own accounts, making the system self-service oriented. This eliminates the need for complex external management and authentication systems, reducing infrastructure complexity while maintaining security through customer-controlled access.

Inventive Principle:

Principle #25Self-service

3Speed

If external systems push deployment to customer accounts, then deployment speed may be faster, but security restrictions block external data traffic

Engineering Contradiction:

Improvedeployment speedVSAvoidsecurity policy restriction

Core Design Contradiction:

SpeedVSObject-affected harmful factors

Solution Approach 1:

The system inverts the deployment direction from external-push to internal-invoke. Deployment tools are pulled into the customer account and executed from within, eliminating the need for external data traffic while maintaining deployment speed through local resource utilization.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The software provider's account serves as an intermediary that hosts deployment tools without requiring direct data traffic to customer accounts. This intermediary mechanism enables fast deployment by keeping tools locally available while blocking harmful external access, as all operations occur within the customer's own account boundaries.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12260205B2Enhanced cloud-computing environment deployment

Publication Date: 2025.03.25 STRATEGY INC

AI summary

Methods, systems, and apparatus, including computer programs encoded on computer-storage media, for enhanced cloud computing deployment. In some implementations, a computer system provides a repository comprising (i) deployment tools configured to provide a deployment application programming interface (API), (ii) a set of container files configured to operate together to provide a server environment, and (iii) configuration data for the container images. The computer system can provide a deployment workflow package that, when invoked for a cloud computing account of the customer, is configured to retrieve the container files, configuration data, and deployment tools from the repository over a communication network and store the retrieved items in the cloud computing account. The deployment workflow package is also configured to run the deployment tools and create deployment infrastructure in the cloud computing account.