Various embodiments migrate a legacy application to a multi-tenant computing environment. In one embodiment, at least one virtualized computing container is instantiated on a host system in a multi-tenant computing environment. An instance of the legacy application is executed within the virtualized computing container. The legacy application having been initially configured to run on premise and serve one tenant at a time. The virtualized computing container securely isolates the executing instance of the legacy application from other executing instances of the legacy application. At least one request received from a first client is sent to the instance of the legacy application executing within the virtualized computing container. The virtualized computing container is quiesced based on at least one quiescing criterion having been satisfied by the instance of the legacy application.

Migrating legacy applications to a multi-tenant computing environment

A service control system manages a set of containers operating within one or more computing hosts. Containers may access a consistent runtime environment regardless which cloud provider the computing hosts come from. Each computing host also runs a control plane agent that interacts with the service control system to provide a set of services to the containers on the computing host and connect the containers to an overlay network of the service control system. The service control system thus may provide networking, firewall, storage, and load balancing services to the various containers. This permits a set of heterogeneous computing hosts to provide consistent services regardless of the underlying computing resources and containers that are managed by the service control system.

Cloud computing service architecture

A system, such as a system of a computing resource service provider, detects changes to a pipeline template package that encodes information associated with application code and infrastructure that may be utilized as part of deploying the application code in stages of a pipeline. An infrastructure template that is usable to provision an execution environment may be generated for a corresponding stage of the development, and may be utilized as part of a process for provisioning an execution environment which may, for example, run tests to verify the quality of the application code.

Deployment of infrastructure in pipelines

Systems, methods, and software described herein provide enhancements for orbital satellite platforms. In one example, an orbital satellite platform includes a plurality of satellite devices each comprising a virtualized execution system configured to execute one or more software payloads as associated virtual nodes. An active satellite device is provided among the plurality of satellite devices and is configured to execute at least an active virtual node, determine state information related to the execution of the active virtual node, and periodically update the state information in a storage satellite device. The storage satellite device is configured to select a level of statefulness for delivery of the state information to a peer satellite device designated as an operational backup for the active satellite device.

Bandwidth aware state transfer among satellite devices

Systems, methods, and software described herein provide enhancements for orbital satellite platform. In one example, an orbital satellite platform includes a plurality of satellite devices configured to establish a pseudo-geosynchronous window corresponding to an underlying zone of interest by at least transferring state information related to execution of a designated software payload from outgoing satellite devices leaving the pseudo-geosynchronous window for receipt by target satellite devices entering the pseudo-geosynchronous window. During orbital passage within the pseudo-geosynchronous window, the target satellite devices are configured to execute the designated software payload in accordance with the state information.

Pseudo-geosynchronous configurations in satellite platforms

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 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 an enterprise catalog service that manages catalogs and portfolios of software products (e.g., desktop applications and server products) on behalf of service provider customer organizations. Through the service, a customer organization administrator may create a portfolio (e.g., a container) and configure the portfolio for subsequent use by end users in the organization, which may include adding products, users, permissions, and constraints on the usage of the products (individually or collectively) to the portfolio for all authorized end users or particular end users. Portfolios may be shared with other administrators by publishing them or through direct notification of sharing. A recipient of a shared portfolio may, after importing it, further restrict access to the portfolio or the use of the products therein, but cannot modify the portfolio itself. Changes made by a portfolio owner may be propagated to authorized users and to portfolio importers automatically.

Portfolios and portfolio sharing in a catalog service platform

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

Technologies are described herein for scanning machine images using a scanning service to identify potential risks. The scanning service may be associated with a service provider network. A scan request is received at the scanning service that requests machine images to be scanned. One or more scans may be performed on each of the machine images. An execution environment may host a machine image during a scan of the machine image. Scan result data associated with the scans is stored. The scan result data may be used to provide scan results to the requestor.

Zachary Thomas Crowell

Papers

Constraints and constraint sharing in a catalog service platform

Catalog service platform for deploying applications and services

Portfolios and portfolio sharing in a catalog service platform

Graph processing service component in a catalog service platform

Scanning machine images to identify potential risks