Ephemeral Cloud Instances with Token-Based Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Persistent computing systems are inefficient and costly due to their inflexible nature, requiring overprovisioning for peak demands, and pose challenges in securing data when serving multiple clients, especially for third-party providers managing large data sets.

Innovation Solution

Implementing ephemeral cloud-based computing resources that can be scaled up or down based on real-time needs, with secure data storage and access management using containers and token-based access control to ensure data isolation and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If persistent computing systems are used to handle large data sets, then data storage and processing capability is ensured, but computing resource efficiency deteriorates due to overprovisioning for peak demands

Engineering Contradiction:
Improvedata storage and processing capabilityVSAvoidcomputing resource efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system transitions from static persistent computing resources to dynamic ephemeral cloud-based computing instances that can be created and terminated based on real-time processing needs. This allows the system to scale resources up during peak demands and scale down during low-utilization periods, optimizing resource efficiency while maintaining data availability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system separates data storage (persistent) from data processing (ephemeral). Data is stored in persistent storage resources while processing is performed by temporary cloud-based instances that are created on-demand, terminated after processing, and their resources released. This segmentation allows independent optimization of storage reliability and processing efficiency.

Inventive Principle:
Principle #1Segmentation

2Productivity

If third-party vendors manage data from multiple enterprises, then resource utilization improves, but data security deteriorates due to potential unauthorized access between clients

Engineering Contradiction:
Improveresource utilizationVSAvoiddata security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements logical isolation by creating separate ephemeral computing instances for each enterprise client. Each instance operates in its own isolated environment with dedicated access to required data subsets, preventing cross-client data access while allowing the third-party vendor to efficiently manage multiple clients using shared infrastructure resources.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary layer (the ephemeral instance creation and management mechanism) between the shared persistent storage and individual clients. This intermediary enforces access control policies, ensuring that each client can only access their own data through their dedicated instance, while the vendor manages the underlying shared resources efficiently.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11470068B2System and methods for securely storing data for efficient access by cloud-based computing instances
Publication Date: 2022.10.11 PWC PRODUCT SALES LLC
  • US11470068B2 patent drawing
  • US11470068B2 patent drawing
  • US11470068B2 patent drawing

AI summary

Systems and methods for securely storing data for efficient access by cloud-based computing instances is provided. In one or more examples, a computing hub can receive one or more access requests to data stored within a persistent data storage computing resources that in connected to the computing hub. The computing hub can be configured to determine if the access request is from an authorized computing resource, and can then generate one or more tokens that provide access to the computing resource. The one or more tokens can include information regarding the IP address of the requesting cloud-based computing resource, and each time that the cloud-based computing resource uses the token to request access to the stored data, the computing hub can check the IP address of the computing resource against the IP address indicated on the token to decide whether or not to grant access to the data.