Agentless Configuration Management Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing configuration management systems are often vendor-specific, hardware-dependent, and rely on agents or daemons that operate outside administrator control, making it difficult to manage configurations across heterogeneous systems, especially those behind firewalls or NATs.

Innovation Solution

A generic, agentless configuration management service implemented as a web service that allows clients to specify and manage configurations across diverse target systems using standardized protocols like HTTP and XML, enabling package generation and delivery independent of specific platforms, and facilitating communication through firewalls and NATs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If vendor-specific configuration management systems are used, then management of specific applications is improved, but adaptability to heterogeneous systems deteriorates

Engineering Contradiction:
Improveconfiguration management capabilityVSAvoidplatform independence
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The configuration management system is designed with a universal architecture that can manage multiple types of applications and operating systems through a common interface. The system uses standardized protocols (HTTP, XML) and abstracted communication mechanisms that work across different platforms, allowing a single system to perform configuration management for diverse applications without requiring vendor-specific implementations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Extent of automation

If agents or daemons are deployed on client systems, then background management tasks are automated, but system security and administrator control deteriorate

Engineering Contradiction:
Improvebackground managementVSAvoidadministrator control
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The invention extracts the configuration management functionality from resident agents/daemons on client systems and consolidates it into a standalone configuration management application. This extracted architecture allows the management application to perform verification tasks and communicate with target systems without requiring persistent background processes on each client, thereby maintaining automation while improving administrator control and system security.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The configuration management system enables target systems to self-verify their configuration states by executing verification logic locally without requiring external agents. The system uses self-service mechanisms where the configuration management application can directly interact with target systems through standardized protocols, eliminating the need for trusted third-party agents while maintaining automated verification capabilities.

Inventive Principle:
Principle #25Self-service

3Device complexity

If agents communicate with remote servers, then centralized management is achieved, but communication through firewalls and NATs deteriorates

Engineering Contradiction:
Improvecentralized management architectureVSAvoidnetwork communication
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The invention introduces an intermediary configuration management application that acts as a mediator between administrators and target systems behind firewalls or NATs. This intermediary uses standardized web protocols (HTTP, XML) that can traverse firewalls and NAT devices, enabling centralized management functionality without requiring direct agent-to-server communication that would be blocked by network security devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Manufacturing precision

If platform-specific configuration systems are used, then optimization for specific hardware is improved, but portability across heterogeneous systems deteriorates

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidcross-platform compatibility
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The configuration management system uses parameter changes to adapt to different platforms while maintaining consistent management functionality. The system dynamically adjusts communication parameters, data formats, and verification methods based on the target system's platform characteristics, allowing accurate configuration management across heterogeneous systems without requiring platform-specific system implementations.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10419289B2System and method for configuration management service
Publication Date: 2019.09.17 AMAZON TECH INC
  • US10419289B2 patent drawing
  • US10419289B2 patent drawing
  • US10419289B2 patent drawing

AI summary

System and method for agentless computing system configuration management in networked environments. A configuration management service may be implemented as a service on a network with a standard network interface. A client may communicate with the service to specify a configuration for a target system, for example through a browser interface. The specified configuration may be stored by the service. The service may generate a package according to the specified configuration. The package may be delivered to the target system via the network. The package may then install the configuration, for example, one or more software, data, or other digital components, on the target systems in accordance with the specified configuration. The clients may request that the service verify and/or update the installed configuration on the target system. The service may, in response, generate an update package for the installed configuration. Target systems may include computer systems and virtual machines.