US 12,754,732 B2Granted

Systems and methods for public cloud service data querying

AssigneeJPMorgan Chase Bank, N.A.

InventorsAlasdair Rae, Ganesh Prabhu, David Thomson, Donnie Kennedy, Ellis Gowan, Krzysztof Malinowski, Sean Oneill, Kaushik Nimmala

Life of this patent

Estimating the term…

patentgrep

Loading patent…

Abstract

In some aspects, the techniques described herein relate to a method including calling, by a first event driven function associated with a spoke account, an inventory interface of the spoke account; writing, by the first event driven function, inventory data received from the inventory interface to a messaging queue, wherein the messaging queue is associated with a hub account; receiving, by a second event driven function, the inventory data from the messaging queue, wherein the second event driven function is associated with the hub account; writing, by the second event driven function, the inventory data to a database, wherein the database is associated with the hub account; executing, by a third event driven function, a query of the database, wherein the query retrieves the inventory data, and wherein the third event driven function is associated with an administrative account; and displaying the inventory data via a front-end application.

Claims18

Dependent claims

A method, comprising:

calling, by a first event driven function associated with a spoke account, an inventory interface of the spoke account, wherein the spoke account is provided by a public cloud service and is a first cloud account having a first cloud-provider account identifier;
writing, by the first event driven function, inventory data received from the inventory interface to a messaging queue, wherein the messaging queue is associated with a hub account, wherein the hub account is provided by the public cloud service, wherein the first event driven function invokes an inventory API that provides an application identifier;
receiving, by a second event driven function, the inventory data from the messaging queue, wherein the second event driven function is associated with the hub account;
writing, by the second event driven function, the inventory data to a first database, wherein the first database is associated with the hub account;
executing, by a third event driven function, a first query of the first database, wherein the first query retrieves the inventory data,
wherein the third event driven function is associated with an administrative account provided by the public cloud service,
wherein the hub account is a second cloud account having a second cloud-provider account identifier, and
wherein each message written to the messaging queue includes message metadata comprising an identifier of the spoke account that wrote the message;
executing, by a front-end application, a second query of a second database, wherein the second database is hosted on a backend of a subscribing organization, and wherein the second query retrieves the identifier of the spoke account based on an identifier of a user;
and
displaying the inventory data via the front-end application.

8 more elements

A system comprising one or more computer processors, wherein the one or more computer processors are configured as a public cloud service, and wherein the one or more computer processors are configured to:

call, by a first event driven function associated with a spoke account, an inventory interface of the spoke account, wherein the spoke account is provided by
the public cloud service and is a first cloud account having a first cloud-provider account identifier;
write, by the first event driven function, inventory data received from the inventory interface to a messaging queue, wherein the messaging queue is associated with a hub account, wherein the hub account is provided by the public cloud service, wherein the hub account is a second cloud account having a second cloud-provider account identifier, wherein the first event driven function invokes an inventory API that provides an application identifier;
receive, by a second event driven function, the inventory data from the messaging queue, wherein the second event driven function is associated with the hub account;
write, by the second event driven function, the inventory data to a first database, wherein the first database is associated with the hub account;
execute, by a third event driven function, a first query of the first database, wherein the first query retrieves the inventory data, and wherein the third event driven function is associated with an administrative account provided by the public cloud service;
executing, by a front-end application, a second query of a second database, wherein the second database is hosted on a backend of a subscribing organization, and wherein the second query retrieves an identifier of the spoke account based on an identifier of a user;
and
displaying the inventory data via the front-end application.

6 more elements

Dependencies are inferred from the claim text.