Amazon Technologies, Inc.

Frederik Christophe Delacourt

Christopher Whitaker

Julien Jacques Ellie

Zachary Thomas Crowell

Quan Binh To

Benjamin David Newman

Richard Curtis Edwards, Jr

A service provider system may implement a notification service that manages actionable notification messages received from other services on behalf of a customer organization and its end users. An IT administrator of the customer organization may create and configure message inboxes to be maintained by the notification service. The messages stored in each inbox may be partitioned by source, type, targeted (authorized) recipients, or an associated message topic. Each message may include an identifier of the inbox to which it is directed, and active elements that, when selected by a recipient, cause a corresponding action to be performed. The service from which a message is received may, in response to a message recipient taking one of the available actions, submit a request to the notification service to update the message state. The notification service may provide APIs through which the other services and message recipients interact with the notification service.

Notification service for managing actionable messages from backend services

A service provider system may implement an enterprise catalog service that manages software products and portfolios of software products on behalf of service provider customer organizations. Through an administrator interface of the service, a customer organization administrator may create constraints on the use of the software products, and each constraint may include one or more rules about how the products can be launched. These may include environmental constraints (specifying a region in which a product launches), restrictions on input parameter values (including the types of resource instances on which a product can be launched), quotas (controlling the number of product installations), or billing constraints. Constraints may be applied on a user-to-product arc or on a portfolio-to-product arc. Constraints may be stored as objects, and reference to those objects may be added to product or portfolio objects. Constraints may be shared across object versions, portfolios, or service provider customer accounts.

Constraints and constraint sharing in a catalog service platform

A service provider system may implement an approval service that manages approval requests received from other services on behalf of a customer organization and its end users. An administrator in the organization may create approval templates that define voting strategies at multiple approval levels and associate them with particular requests (individually, or by product, portfolio, project, action, message topic, workflow, or request type). The administrator may create approval groups whose members are authorized to respond to particular requests. Each approval template (or approval level) may include a different voting strategy or be associated with a different approval group. The approval system may support pre-notification of subsequent approval levels, auto-escalation, or auto-expiration. The approval service may employ a notification service to manage actionable notification messages that include approval requests. Members of approval groups may retrieve requests and select from available actions (e.g., approve, deny, or request more information).

Growing community of inventors

Mercer Island, WA, United States of America

Frederik Christophe Delacourt