Dynamic Isolation Routing for Secure Code Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed systems, executing custom code tasks such as ETL processing poses safety concerns due to the risk of malicious or destructive code, and existing cloud or network-based service computing platforms do not adequately manage these risks, burdening users with resource provisioning and management.

Innovation Solution

Implementing an execution engine that determines isolation types for executing code portions, dynamically routing code execution to computing resources configured with appropriate isolation levels, such as physical, logical, or multi-tenant isolation, to contain the impact of malicious or disruptive code, thereby ensuring the safety of computing resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If custom code tasks are executed in distributed systems without adequate isolation, then productivity and ease of operation are improved, but security and reliability deteriorate due to risks of malicious or destructive code

Engineering Contradiction:
Improveease of executing custom code tasksVSAvoidsecurity of computing resources
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments computing resources into isolated execution environments (containers, virtual machines, or sandboxed processes) where custom code can be executed without direct access to the host system or other clients' resources. This segmentation allows users to easily execute custom code while maintaining security boundaries that prevent malicious or erroneous operations from affecting the broader system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary execution layer (such as a container runtime or virtualization management system) that sits between the user-submitted code and the physical computing resources. This intermediary enforces isolation policies, manages resource allocation, and prevents direct access to sensitive system components, thereby enabling ease of code execution while preserving system reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If isolation mechanisms are implemented to protect against malicious code, then reliability and security are improved, but device complexity and management burden increase

Engineering Contradiction:
Improvesecurity of computing resourcesVSAvoidcomplexity of resource provisioning and management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service automation where the execution environment automatically provisions, configures, and manages isolation resources based on policy rules. The system autonomously handles container creation, resource allocation, and isolation enforcement without requiring users to manually configure complex isolation parameters, thereby maintaining high security while reducing management complexity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent employs parameter-based isolation models where security and resource constraints are defined through configurable parameters (such as CPU limits, memory allocations, network policies) rather than complex structural configurations. This allows the system to maintain reliable isolation while simplifying management by adjusting parameters automatically based on workload characteristics and security policies.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If uniform high-level isolation is applied to all code executions, then security is improved, but productivity and resource efficiency deteriorate due to over-provisioning

Engineering Contradiction:
Improvesecurity of computing resourcesVSAvoidefficiency of code execution
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies differentiated isolation strategies tailored to specific code execution contexts. Trusted or verified code may execute in less isolated environments with higher resource efficiency, while untrusted or high-risk code receives stronger isolation. This local quality approach maintains security for critical executions while improving overall productivity by avoiding unnecessary isolation overhead for safe operations.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements dynamic isolation adjustment where the level of isolation is adapted based on runtime characteristics such as code trust level, resource requirements, and security risk assessment. The system can dynamically provision or relax isolation constraints during execution, allowing high-productivity execution for safe code while maintaining strong security isolation when needed, thereby optimizing both reliability and efficiency.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11036560B1Determining isolation types for executing code portions
Publication Date: 2021.06.15 AMAZON TECH INC
  • US11036560B1 patent drawing
  • US11036560B1 patent drawing
  • US11036560B1 patent drawing

AI summary

Isolation types may be determined for resources that execute portions of code. Code may be received via a network-based interface from a client for execution. An execution plan for the code may be generated and evaluated to determine one or more isolation types for computing resources that execute the code. The computing resources that are configured to provide the determined isolation types may then be identified and execution of the code initiated at the identified computing resources.