Event-Driven API Call Manager for Cloud Account Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for managing multiple cloud accounts across different service providers require substantial computing resources and manual inputs to keep accounts and policies up-to-date, especially as organizations grow and add new accounts, leading to inefficiencies in processing and memory usage.
Innovation Solution
A system that integrates new accounts created at a service provider network with a third-party application using event-driven API call managers, reducing the need for continuous API queries by leveraging the service provider network's resources for 'bottom-up' integration across multiple cloud platforms, thereby minimizing processing and memory requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous code execution is used to manage accounts and policies, then account management functionality is maintained, but processing resources and memory consumption increase substantially
Solution Approach 1:
The system transitions from continuous code execution to event-driven periodic action, where the queuing service only executes code when account creation or policy change events occur. This event-triggered mechanism maintains account management functionality while eliminating unnecessary continuous processing, thereby reducing processing resources and memory consumption substantially.
2Ease of operation
If manual inputs and continuous API queries are used to notify third-party applications of new accounts, then account integration is achieved, but time and computing resources increase
Solution Approach 1:
The system implements preliminary action by having the queuing service automatically detect account creation events and trigger integration processes without waiting for manual inputs or continuous polling. The event-driven architecture pre-configures the integration workflow, so when an account is created, the third-party application is notified immediately through automated event processing, eliminating delays associated with manual operations and continuous API queries.
3Reliability
If complex policies are applied to new account types, then proper access control is ensured, but system complexity and processing requirements increase
Solution Approach 1:
The queuing service acts as an intermediary between account creation events and policy application processes. When a new account is created or a policy changes, the event-driven architecture routes the appropriate policy enforcement actions through the queuing service, which manages the complexity of policy evaluation and application. This intermediary approach ensures proper access control while containing system complexity within the event management layer rather than propagating it throughout the entire system.
Data Source
AI summary
Technologies are disclosed for integrating an account with a third-party application. Upon completion of an account creation procedure or an account configuration procedure at a service provider network, a system may automatically (e.g., absent additional manual inputs) integrate the new account and/or the account configuration with the third-party application, for instance, such that the new account and/or the account configuration is replicated across multiple cloud accounts managed by the third-party application. The service provider network may comprise an organization account creator, an account configurer, an event monitor for detecting an account-related event (e.g., occurring at the organization account creator and/or the account configurer), and an event-driven API call manager for receiving an event message from the event monitor, and executing code previously stored in an non-executing state to send one or more API calls to the third-party application for integrating the account with the third-party application.