Primary-Account Backup Plans for Unified Cross-Account Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Organizations with multiple accounts on a provider network face challenges in managing data backup policies independently, leading to potential compliance violations, manual effort duplication, and lack of a unified view of data backups across the organization.

Innovation Solution

Implementing a cross-account data management (CAM) service that allows a primary account to manage data protection plans across multiple accounts, enabling centralized policy application, compliance monitoring, and reducing operational overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each account manages data backup policies independently, then account-level autonomy is maintained, but compliance violations occur and unified monitoring is lost

Engineering Contradiction:
Improvecompliance adherenceVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple independent account backup management operations into a single cross-account management system. A primary account can create backup plans that are automatically applied to multiple member accounts, consolidating what would otherwise be separate management processes into one unified system. This resolves the contradiction by maintaining compliance through centralized control while reducing the complexity of managing each account separately.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The cross-account backup plan system provides universal functionality that allows a single backup policy to serve multiple accounts simultaneously. The primary account's backup plan can be applied across numerous member accounts, making the backup management system multi-functional and adaptable to various organizational structures. This enables compliance adherence across all accounts while simplifying the overall management complexity.

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

2Ease of operation

If backup policies are managed independently across accounts, then account-specific customization is possible, but manual effort increases and time is consumed

Engineering Contradiction:
Improveoperational efficiencyVSAvoidconfiguration time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-configuring backup plans in the primary account before they are applied to member accounts. The backup plan template is created once with all necessary parameters, and then automatically distributed and applied across multiple accounts. This preliminary configuration action eliminates the need for repetitive manual setup in each account, significantly reducing operational effort and time consumption.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by replicating the backup plan configuration from the primary account to multiple member accounts. Instead of manually configuring each account from scratch, the system copies the proven backup policy template across accounts, ensuring consistency while dramatically reducing the time and effort required for configuration. This copying mechanism maintains ease of operation while minimizing time loss.

Inventive Principle:
Principle #26Copying

3Loss of information

If multiple accounts are managed separately, then account-level control is maintained, but a unified view of data backups is lost

Engineering Contradiction:
Improvevisibility of backup statusVSAvoidsystem architecture
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The primary account acts as an intermediary that bridges the gap between individual member accounts and the organization's overall backup strategy. The primary account creates and manages backup plans that are applied across member accounts, providing a centralized control point that maintains visibility of all backup operations. This intermediary structure enables unified monitoring and information visibility while managing the complexity of coordinating multiple accounts.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If administrators configure backup plans in each account, then account-specific requirements are met, but administrators are diverted from business-critical tasks

Engineering Contradiction:
Improveadministrator productivityVSAvoidbackup management ease
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent extracts the backup management function from individual account operations and consolidates it at the cross-account level. By taking out the repetitive configuration tasks from each account and centralizing them in the primary account, administrators are freed from mundane setup work. This extraction enables administrators to focus on higher-value business-critical tasks while the cross-account system handles the routine backup management automatically.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20250247396A1Using a primary account to implement a resource management plan across accounts of an organization
Publication Date: 2025.07.31 AMAZON TECH INC
  • US20250247396A1 patent drawing
  • US20250247396A1 patent drawing
  • US20250247396A1 patent drawing

AI summary

A cross-account data management (CAM) service of a provider network may assign, to a primary account of an organization of a client, permission to manage resource management plans for other accounts of the organization. The CAM service may specify, using the primary account (e.g., by an administrator using the primary account), a resource management plan (e.g., data backup plan) The CAM service may indicate, using the primary account, multiple accounts of the organization that the resource management plan is to be implemented for. The CAM service may cause, based on the permission assigned to the primary account, the resource management plan to be implemented for the different accounts of the organization (e.g., by causing execution of jobs to implement a backup plan).