Amazon Technologies, Inc.

Microsoft Technology Licensing, LLC

Quan Binh To

Julien Jacques Ellie

Zachary Thomas Crowell

Benjamin David Newman

Christopher Whitaker

Andrew L Silverman

Sam J George

Shiraz M Somji

Benjamin M Westbrook

Koji Kato

Vladimir V Smirnov

Divij Gupta

Frederik Christophe Delacourt

Brigette Krantz

Alex Mogilevsky

Richard Curtis Edwards, Jr

Mark Douglas Harper

Rudolph Balaz

Sheshadri Supreeth Koushik

Christopher Michael Hahn

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. A graph processing service of the enterprise catalog service may create a graph representation of the enterprise catalog service data, including principals, product listings, portfolios, and constraints (and the relationships between them) that may be used to manage access control, launch contexts, and searches within the enterprise catalog service. A primary (key-value) store may maintain an adjacency list and a secondary index of de-normalized edges. A secondary (document) store may maintain the de-normalized edges. In response to various queries directed to the graph processing service, the service may query the adjacency list or the secondary index. For example, one query may return a list of products that an end user can access, and another may return a count of products within a portfolio.

Graph processing service component in a catalog service platform

A service provider system may implement an enterprise catalog service that manages catalogs or portfolios of software products (e.g., desktop applications and server products) on behalf of service provider customer organizations. Through the enterprise catalog service, an administrator in a customer organization may discover, select, and ingest products (e.g., based on their features, pricing, and terms), and may add them to catalogs or portfolios for subsequent use by end users in the organization. The administrator may apply constraints on product use and limit product access to particular end users. The products may include third party products that are made available through the enterprise catalog service and a customer's own applications. The enterprise catalog service may monitor usage of third party products and bill the customer organization. Products managed by the enterprise catalog service may be deployed through an application fulfillment platform or resource stack management platform.

Catalog service platform for deploying applications and services

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).

Approval service in a catalog service platform

Methods, systems, and computer-readable media for implementing template generation for deployable units are disclosed. An indication of a deployable unit is received by a catalog system. A deployment template is generated that represents one or more directives for deploying the deployable unit. The deployment template is generated based at least in part on analysis of the deployable unit by the catalog system. The deployable unit is deployed to one or more resources of a multi-tenant provider network. The deployable unit is deployed based at least on part on the directives of the deployment template.

Template generation for deployable units

A system and process for capturing and rendering ink is described. An ink canvas object may contain none, one, or more objects or elements and may specify the z-order of the objects or elements. The ink canvas object may host a variety of objects or elements and, therefore, provide ink functionality to the objects or elements, even though the objects or elements themselves may not have ink functionality. The ink canvas object is attached to an ink editor that has an associated modifiable ink editor behavior, whereby ink specific behaviors are collected in the ink edit behavior.

Ink editing architecture

A system for testing software modules is provided. A user enters parameter values that will be tested into a spreadsheet. The spreadsheet application generates an XML data file including the parameter values arranged into a table. A test shell extracts test cases from the XML data file and converts the data into a testing object for use by a test engine.

Category partitioning markup language and tools

A system and method for erasing ink is described. Using an erasing contour, the system determines closest points which come close to or contacts the erasing contour when it encounters an ink stroke. Portions of an ink stroke may then be erased when the erasing contour contacts the ink stroke.

Growing community of inventors

Redmond, WA, United States of America

Quan Binh To